AI agent
MCP Server + CatCaster
Technical reference for CatCaster MCP
One HTTP MCP endpoint powers every agent page. Discovery, dynamic client registration, and workspace-scoped roles are documented in docs/mcp-oauth.md.
Example chat
via CatCaster MCP · MCP Server
How to connect MCP Server
- Add only the server URL to OAuth-capable clients: https://www.catcaster.com/api/mcp
- Client discovers protected-resource metadata and opens CatCaster consent.
- Legacy clients may use Authorization: Bearer with a developer API key from Settings → Developer.
- Call tools/list after connect; mutating tools respect workspace role and idempotency keys.
CatCaster MCP server URL
https://www.catcaster.com/api/mcp
Cursor (.cursor/mcp.json)
{ "mcpServers": { "catcaster": { "url": "https://www.catcaster.com/api/mcp" } } }
OAuth sign-in is recommended. Developer API keys in Settings → Developer work for clients that cannot open the browser consent flow. Keep a human in the loop before publish_post and send_inbox_reply.
What you can do with MCP Server
OAuth 2.1
Supabase-backed authorization with browser consent—no social passwords in MCP.
Tool surface
Posts, editorial proposals, knowledge, calendar, analytics, inbox, and upload_media.
Prompts
Built-in prompts: review_new_proposals, prepare_weekly_content, weekly_performance_review, triage_inbox.
Safety
Published posts cannot be deleted via MCP; publish and inbox send require idempotency keys and human intent.
Channels agents can reach
MCP tools and prompts
Workspace and channels
list_workspaces · list_channels · get_usage · list_calendar · get_analytics
Brand and editorial
get_brand_context · list_knowledge · list_content_proposals · discover_content_proposals · review_content_proposal · create_post_from_proposal
Posts and publishing
list_posts · create_post · update_post · validate_post · schedule_post · publish_post · upload_media
Performance and inbox
list_published_content · get_publication · list_strategy_proposals · list_inbox_conversations · draft_inbox_reply · send_inbox_reply
Built-in MCP prompts
review_new_proposals · prepare_weekly_content · weekly_performance_review · triage_inbox
Full OAuth and discovery details: docs/mcp-oauth.md in the CatCaster repository.
Example prompts
- Read catcaster://…/brand-context resource for my workspace and summarize voice rules.
- Explain idempotency requirements for publish_post.
Agents should run validate_post and show drafts before scheduling or publishing. CatCaster MCP does not generate images or video—attach media the agent already has via upload_media or HTTPS URLs on create_post.
Frequently asked questions
- Is CatCaster preinstalled in ChatGPT or Claude?
- No. You add CatCaster as a custom MCP connector (or use OAuth from a client that supports remote MCP). Sign in with your CatCaster account when the client opens the consent flow.
- Will the agent publish without asking me?
- CatCaster expects a human in the loop. Agents should run validate_post and show drafts before schedule_post or publish_post. Inbox send_inbox_reply should only run after you explicitly approve the draft.
- Can agents generate images or video inside MCP?
- Not through CatCaster MCP today. Agents can attach media they already have via upload_media (HTTPS URL) or URLs on create_post. Image and video generation in the product UI is separate from MCP.
- What platforms can agents reach?
- Any channel already connected in your workspace—Instagram, Facebook, Threads, TikTok, LinkedIn, X, YouTube, Pinterest, and your CatCaster blog, subject to each platform’s API limits documented on our platform guides.
- Where is OAuth documented?
- See docs/mcp-oauth.md in the CatCaster repository for discovery URLs, environment variables, and verification curl commands.
- What protocol versions are supported?
- The endpoint negotiates MCP initialize versions and supports stateless HTTP discovery per current MCP specs. API keys in query strings are deprecated in favor of Authorization headers.