Automating with AI agents
How do I connect Cast to Claude, Cursor or another AI agent?
Add the Cast MCP server — https://cast-mcp.mubert.com/mcp — to your assistant and approve it in the browser. No token to copy: one command for Claude Code, one JSON block for everything else. After that you can just ask it to produce your episode.
Cast speaks MCP (Model Context Protocol) — the standard way AI assistants call tools. Any MCP client works: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, n8n, or your own code.
Add https://cast-mcp.mubert.com/mcp as an HTTP MCP server. The first time the assistant uses it, a browser page opens: sign in to Cast and click Allow. Cast creates a token just for that assistant — with "Let it spend credits" off unless you tick it — and lists it in Settings → API & MCP, where you can revoke it any time.
Claude Code
One command — your browser opens once to approve it:
claude mcp add --transport http cast https://cast-mcp.mubert.com/mcp
Claude Desktop and claude.ai
Settings → Connectors → Add custom connector, paste https://cast-mcp.mubert.com/mcp and click Connect — the Cast page opens to approve it.
Cursor, Windsurf, VS Code
Add an entry to the mcpServers block of your client config (Windsurf calls the field serverUrl):
{ "mcpServers": { "cast": { "type": "http", "url": "https://cast-mcp.mubert.com/mcp" } } }
Restart the client, approve the connection in the browser, and "cast" appears in its tool list.
Teach the assistant how to use it
The tools carry the rules; the cast-mcp skill carries the strategy — the order of calls that keeps a session cheap, and asking you before anything is paid. Install it with the other Mubert skills: npx skills add MubertAI/skills
n8n, CI, scripts, your own agent
A client that cannot open a browser uses a token instead. Settings → API & MCP → Create token, then send it as an Authorization: Bearer <token> header to the same endpoint:
claude mcp add --transport http cast https://cast-mcp.mubert.com/mcp --header "Authorization: Bearer <your token>"
The API itself is plain REST if you would rather call it directly — the MCP server is a thin layer over it.
Last updated