Cannon Studio MCP Server

Public Cannon Studio MCP for product, pricing, workflow, model, and API answers.

Tools

Last Updated

Jun 14, 2026

What is the Cannon Studio MCP Server?

The Cannon Studio MCP server gives AI agents structured, permission-aware access to Cannon Studio through the Model Context Protocol. With 15 pre-built actions, agents can read, create, and update Cannon Studio data on behalf of authorized users.

Willow ships the Cannon Studio MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Cannon Studio is being used by every AI agent in your stack.

Tools

search

Search public Cannon Studio knowledge when a user asks about products, workflows, pricing, models, comparisons, use cases, or developer API docs. Public read-only: no auth, no state changes, no charges; call fetch with a returned id when full source-backed text is needed.

fetch

Fetch one public Cannon Studio knowledge record by id after search. Public read-only: no auth, no state changes, no charges; use search first when you do not already have a record id.

list_capabilities

List public Cannon Studio capabilities for an audience, workflow, or output type. Public read-only: no auth, no state changes, no charges; use search or fetch when the user needs deeper source text.

recommend_workflow

Recommend a Cannon Studio workflow for a stated creative or developer goal. Public read-only: no auth, no state changes, no charges; use this for planning, not to create generation jobs.

compare_alternatives

Compare Cannon Studio's fit against named alternatives for a use case. Public read-only: no auth, no state changes, no charges; it returns approved positioning and cautions agents not to invent competitor claims.

get_pricing_context

Explain public Cannon Studio pricing, credits, plans, and usage tradeoffs. Public read-only: no auth, no state changes, no charges; use list_offerings or get_checkout_link only when the user asks for available purchase paths.

list_offerings

List public Cannon Studio plans, credit packs, and team offerings. Public read-only: no auth, no state changes, no charges; returns first-party checkout or inquiry URLs without creating Stripe sessions or granting credits.

get_checkout_link

Return the first-party Cannon Studio checkout or inquiry URL for a selected offering. Public read-only: no auth, no state changes, no charges; use list_offerings first to get a valid product_key.

get_model_availability

List public Cannon Studio model availability by product surface. Public read-only: no auth, no state changes, no charges; model availability is surface-specific and does not guarantee account eligibility or remaining credits.

list_toolkits

List first-party Cannon Studio image, video, audio, subtitle, editing, Composer, and 3D toolkit surfaces, including which ones are developer-API operations and which should be opened in the app or routed through Director Mode. Public read-only: no auth, no state changes, no charges.

1 2

1–10 of 15 tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Cannon Studio MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-cannon-studio": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cannon-studio"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-cannon-studio": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cannon-studio"
    }
  }
}

Claude Code

CLI

claude mcp add willow-cannon-studio --transport http https://<org>.mcp-s.com/mcp/mcp/cannon-studio

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/cannon-studio",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Cannon Studio

Willow adds the layer Cannon Studio and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Cannon Studio MCP Server FAQ

What is the Cannon Studio MCP server?

The Cannon Studio MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Cannon Studio data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Cannon Studio MCP server different from the official one?

The official Cannon Studio MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Cannon Studio MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Cannon Studio MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Cannon Studio, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Cannon Studio actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Cannon Studio MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Cannon Studio MCP locally, you'll see it.

What does the Cannon Studio MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Cannon Studio MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.