AI agent

Agents CLI + CatCaster

HTTP and client CLIs—no CatCaster binary

Headless automation uses the same MCP URL. Prefer OAuth in interactive clients; use API keys only where browser login is impossible.

Example chat

Show curl to call validate_post on a draft ID using my API key.
Use POST /api/mcp with tools/call and your Bearer key; see Settings → Developer for the key format.

via CatCaster MCP · Agents CLI

CatCaster — Compose
CLI and HTTP clients update the same drafts as the web app.

How to connect Agents CLI

  1. Claude Code: claude mcp add with SSE transport to the CatCaster URL.
  2. Codex / custom scripts: JSON-RPC POST to /api/mcp with Bearer API key.
  3. Claude Desktop: add the remote MCP URL in claude_desktop_config.json — same as Cursor.
  4. Never commit API keys; rotate keys in Settings → Developer if leaked.

CatCaster MCP server URL

https://www.catcaster.com/api/mcp

cURL tools/list (API key)

curl -X POST https://www.catcaster.com/api/mcp \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

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 Agents CLI

  • Claude Code

    Interactive terminal sessions with OAuth when available.

  • curl / HTTP

    tools/list and tool calls for debugging integrations.

  • Claude Desktop

    Add the remote MCP URL directly — no local bridge script needed.

  • No catcaster-cli

    We do not ship a standalone npm binary named catcaster—clients speak MCP directly.

Channels agents can reach

Connect accounts once in CatCaster. Agents post only to channels already linked in your workspace.

Example prompts

  • Document the difference between OAuth and API key authentication for CLI usage.
  • Show how to set up Claude Desktop with the remote MCP URL.

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.
Is there a CatCaster CLI npm package?
No. Use MCP-compatible clients (Claude Desktop, Claude Code, Cursor, curl) — all connect to the same remote MCP URL with OAuth or API keys.

Other AI agents

Browse all agents →

Keep the energy. Lose the chaos.

Join 1,400+ founders on the early access list. The first 200 members lock in 50% off — for life.

Try Beta

No Card Required

Already have an account? Log in

Free forever plan · No credit card · Cancel in two clicks

Privacy PolicyTerms of Service