Internal — copy into Article Settings, then delete before publishing.
SEO description: Which AI clients can connect to the Fullcast MCP server, and how to connect one.
Tags: mcp, ai-assistant, setup, admin, claude, integration
Related articles: Enable AI features (enable-ai-features), Fullcast MCP prompt library (fullcast-mcp-prompt-library), Fullcast MCP office hours recording guide (fullcast-mcp-office-hours-recording-guide), Application settings reference (tenant-settings)
MCP is an open protocol that standardizes how applications provide context to LLMs. Use the MCP to connect AI clients, like Claude, to Fullcast.
Before you begin
AI features are enabled for your tenant. A tenant admin turns these on under Settings > Application Settings > AI & Agents by switching Enable AI Assistant Features on.
You have an AI client that supports remote MCP servers.
You know what your Fullcast permissions cover. The MCP acts as you: if you cannot do something in the Fullcast user interface (UI), you cannot do it through the MCP.
AI clients you can connect
You can connect any AI client that supports remote MCP servers. Fullcast does not restrict which client you use. Claude is the client Fullcast tests against, so the steps below cover Claude; for any other client, follow that client's own instructions for adding a remote MCP server.
Access is controlled by your Fullcast sign-in, your tenant's AI features setting, and your own permissions — not by which client you connect from.
Some desktop clients finish signing in by handing off to their own custom link. Fullcast completes this handoff for Claude, Cursor, VS Code, Cline, and MCP Inspector. A desktop client that uses a different custom link cannot finish signing in yet. Clients that sign in through a browser are not affected.
Connect Claude to Fullcast
Set up the custom connector in Claude—add the following Fullcast URL for the connector's remote MCP server URL: https://app.fullcast.io/mcp.
Sign in to Fullcast to authenticate the connection.