The Cast AI Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Desktop, to interact directly with the Cast AI API.

What is MCP?

Model Context Protocol (MCP) is an open standard that allows AI applications to securely access external data sources and tools. The Cast AI MCP server provides AI agents with:

• Direct API access to Cast AI functionality
• Real-time data from your Cast AI account
• Code generation assistance for Cast AI integrations

Cast AI MCP server setup

Cast AI hosts a remote MCP server at https://docs.cast.ai/mcp. Configure your AI development tools to connect to this server.

{
  "mcpServers": {
    "castai": {
      "url": "https://docs.cast.ai/mcp",
      "headers": {
        "X-API-Key": "<your-cast-ai-api-key>"
      }
    }
  }
}

Authentication

The Cast AI MCP server uses your Cast AI API key to authenticate requests to your account. Pass the key using the X-API-Key header, as shown in the configuration examples above.

Obtaining an API key

Generate an API access key from the Cast AI console under User > API keys. For details, see Authentication.

Testing your MCP setup

Once configured, test your MCP server connection:

1. Open your AI editor (Cursor, Windsurf, etc.)
2. Start a new chat with the AI assistant
3. Ask about Cast AI — try a prompt like:
   • "List my Cast AI clusters."

The AI should now have access to your Cast AI account data through the MCP server.

Troubleshooting

If the MCP server is not responding or returning errors, check the MCP server logs for your client before investigating further.

After reviewing logs, also verify that:

• Your API key is valid and has not been deleted or disabled
• The header value in your config does not include extra spaces or line breaks
• You fully quit and relaunched your AI editor after updating the config file — most clients do not reload the MCP configuration without a restart