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; generation tools require a developer API key.
Connection URLs
Use the Streamable HTTP endpoint for ChatGPT Developer Mode, Codex, OpenAI Responses API remote MCP, MCP Inspector, and other compatible clients.
MCP endpoint: https://www.cannonstudio.app/mcp
Health check: https://www.cannonstudio.app/mcp/health
Registry metadata: https://www.cannonstudio.app/mcp/server.json
OpenAPI schema: https://www.cannonstudio.app/api/v1/openapiPublic read-only tools
These tools answer from public Cannon Studio pages, guides, assistant knowledge, model availability, and developer docs.
- search
- fetch
- list_capabilities
- recommend_workflow
- compare_alternatives
- get_pricing_context
- get_model_availability
- get_api_operation
Authenticated tools
These tools forward a developer API key and can touch account/request state. They are not marked read-only.
- 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
Privacy and registry setup
Public tools do not read private workspaces, projects, billing records, or user assets. 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.