MCP

Connect agents to Cannon Studio source material.

The Cannon Studio MCP server gives AI agents a public, source-backed way to answer prospect questions about workflows, pricing, model availability, comparisons, and the developer API. Public tools are read-only; authenticated tools use OAuth account linking or developer API keys.

Endpoint
https://www.cannonstudio.app/mcp
Registry name
app.cannonstudio/cannon-studio
Knowledge records
819

Connection URLs

Use the Streamable HTTP endpoint for ChatGPT Developer Mode, Codex, OpenAI Responses API remote MCP, MCP Inspector, and other compatible clients.

This serverless endpoint supports request/response Streamable HTTP over POST. Plain browser GET requests return endpoint metadata, HEAD requests return 204, and standalone SSE GET requests with Accept: text/event-stream return the protocol-defined 405 because long-lived standalone SSE is not offered. Use the health URL below for web-style probes.

MCP endpoint: https://www.cannonstudio.app/mcp
Health check: https://www.cannonstudio.app/mcp/health
Registry metadata: https://www.cannonstudio.app/mcp/server.json
OAuth resource metadata: https://www.cannonstudio.app/.well-known/oauth-protected-resource
OAuth server metadata: https://www.cannonstudio.app/.well-known/oauth-authorization-server
OpenAPI schema: https://www.cannonstudio.app/api/v1/openapi

Public read-only tools

These tools answer from public Cannon Studio pages, guides, assistant knowledge, model availability, developer docs, and public offering data. Checkout links are first-party Cannon Studio URLs only; they do not charge the user or create Stripe sessions from MCP.

  • search
  • fetch
  • list_capabilities
  • recommend_workflow
  • compare_alternatives
  • get_pricing_context
  • list_offerings
  • get_checkout_link
  • get_model_availability
  • list_toolkits
  • get_api_operation

Authenticated tools

These tools use OAuth account linking or a developer API key and can touch account/request state. Billable creation requires confirmation plus a max credit cap. No MCP cancellation tool is exposed.

  • api_status
  • estimate_generation_cost
  • create_generation_request
  • get_generation_request

Responses API smoke test

curl https://api.openai.com/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
    "model": "o4-mini-deep-research",
    "input": "Search Cannon Studio for the best workflow for UGC ads with reusable characters.",
    "tools": [{
      "type": "mcp",
      "server_label": "cannon_studio",
      "server_url": "https://www.cannonstudio.app/mcp",
      "allowed_tools": ["search", "fetch"],
      "require_approval": "never"
    }]
  }'

Test prompts

What is the best Cannon Studio workflow for a UGC ad campaign with reusable characters?
Compare Cannon Studio to Runway for an agency that needs review loops and finishing tools.
Which Cannon Studio surfaces expose Sora 2 or other video models?
Show me the developer API operation for narration generation.
How do Cannon Studio credits work for video and audio generation?
List Cannon Studio offerings and give me the checkout link for Creator monthly.

Privacy and registry setup

Public tools do not read private workspaces, projects, billing records, user assets, payment details, or API keys. Offering and checkout-link tools do not grant credits, create Stripe sessions, or process payment inside MCP. To publish with HTTP/domain authentication, set MCP_REGISTRY_AUTH_RECORD to the official registry record and verify it at /.well-known/mcp-registry-auth.