Skip to main content
Log in

Cust MCP server setup

Connect Claude, ChatGPT, Claude Code, or another AI app to Cust. Set up MCP with OAuth, choose your regional endpoint, and manage access.

The Cust MCP server uses the Model Context Protocol (MCP) to bring customer context and Cust tools into your AI app. Connections use your Cust access and can include tools that change workspace data. Your AI app must support remote MCP servers with OAuth.

Enable AI apps

An Admin or Owner must open Settings → Workspace → AI app access and turn on Allow AI apps to connect. The switch saves immediately. This page is available when Cust MCP is included in the workspace's enabled features.

Members can then open Settings → You → AI apps for the server URL, setup steps, and their connected apps. If access is turned off, ask a workspace admin to enable it.

Connect your AI app

  1. Open Settings → You → AI apps and copy the Server URL. Setup tabs cover Claude, ChatGPT, Claude Code, and other apps. Your AI app must support remote MCP over Streamable HTTP with OAuth; its plan and workspace policies can affect availability. The regional endpoints are:

    RegionMCP endpoint
    UShttps://api.us.cust.co/mcp
    EUhttps://api.cust.co/mcp
  2. Add that remote MCP server in your AI app, start authorization, and sign in to Cust.

  3. On the Connect an AI app screen, check the app name and return destination.

  4. If you belong to more than one organization, choose the one you want the app to access. Click Allow.

  5. Return to the AI app and try a focused question, such as “Summarize the open action items for Acme.”

If the request expires, start the connection again from your AI app. If the organization is unavailable, check that its administrator has enabled AI app access.

Access and approvals

The connection belongs to your user and the selected organization. Available tools follow your access and the workspace's enabled capabilities. Customer-memory tools can provide a company brief and its action items, and returned record references include links back to Cust.

Saved browser logins are not exposed through the MCP server.

Approvals are handled by the external AI app. Cust runs incoming MCP tool requests without an additional in-chat confirmation, so review the AI app's tool permissions before allowing changes. MCP tool use is recorded in Cust's audit log and usage accounting.

Manage connected apps

In Settings → You → AI apps, Connected apps lists your connections with their connection date and last activity. Select Revoke and confirm to sign an app out. Reconnecting requires a new sign-in.

Admins and owners can review every member's connections and revoke individual connections in Settings → Workspace → AI app access. Turn off Allow AI apps to connect to stop all AI app access for the workspace. Existing connections stop working while it is off. Removing or deactivating a member also prevents their connections from accessing that workspace.

For tools that your Cust Assistant calls in another service, see Assistant connectors.