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
Confirm the following:
MCP access is enabled for your tenant.
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.
Note
Leave Advanced settings blank. Claude offers optional OAuth Client ID and OAuth Client Secret fields; Fullcast does not use them, and entering values there prevents the connector from connecting. The server URL is the entire configuration.
Sign in to Fullcast to authenticate the connection.
Troubleshooting
The connector will not connect after setup
Check whether an OAuth Client ID or OAuth Client Secret was entered under Advanced settings in Claude. Fullcast does not issue these, and any value in those fields stops the connection from completing. Remove the connector, add it again with only the server URL, and sign in to Fullcast when prompted.
Your IT or security team asks for the OAuth client ID and secret
There is none to provide. Your AI client registers itself with the Fullcast MCP server automatically, and Fullcast authenticates you through your Fullcast sign-in in the browser rather than through a static credential stored in the client. The server URL is the full configuration.
A connector that was working now says it is not connected
