Install the Perform.AI MCP server

In ChatGPT, add the Perform.AI plugin from the Plugins page. Every other client connects manually with one URL:

https://mcp.perform.ai/mcp

No trailing slash. Use .../mcp, not .../mcp/.

Authentication is OAuth: on first connection your client opens a Perform.AI sign-in page. Sign in with your Perform.AI username and password, or with Sign in with Google. You need a Perform.AI account belonging to at least one organization; after signing in, select the organization the session should act on.

The Claude directory listing is under review. Once it’s approved, the connector becomes discoverable in Claude and the manual steps below become optional. See availability.

ChatGPT

Perform.AI is available as a plugin in ChatGPT. The plugin connects to https://mcp.perform.ai/mcp-invoke, the URL its listing shows. See Tools in the ChatGPT plugin for how it differs from https://mcp.perform.ai/mcp.

In the ChatGPT sidebar, select Plugins.
Search for Perform.AI, then select + next to Perform.AI. Once added, it appears under Installed.
Sign in to Perform.AI when prompted. It’s the same sign-in as every other client: your Perform.AI username and password, or Sign in with Google.
In a conversation, add Perform.AI to your message and ask a question, for example: “Which carriers had the most delayed deliveries to Germany in July 2026?”
If you belong to more than one organization, the assistant lists them and asks which one to use.

Plugins need a ChatGPT plan that supports them. In ChatGPT Business and Enterprise workspaces, an admin may need to make the plugin available before members can add it. For workspace admins: on the Perform.AI plugin page, Availability sets the Workspace default for everyone in the workspace: Available (members add it themselves) or Installed. The plugin page also lets you review Permissions, turn individual Tools on or off, and choose how New tools are handled.

ChatGPT lists Select organization under Write tools because it changes which organization the session acts on. It doesn’t modify your Perform.AI data. Turning it off prevents the assistant from selecting an organization, so leave it on.

Claude

Claude (web, desktop, and mobile):

Go to Settings → Connectors and select Add custom connector.
Name it Perform.AI and enter the server URL: https://mcp.perform.ai/mcp.
Select Add, then Connect. The Perform.AI sign-in opens; sign in and approve.
In a chat, enable the connector from the tools menu and try: “Which carriers do we have configured?”

Claude Code (CLI):

claude mcp add --transport http perform-ai https://mcp.perform.ai/mcp

Then run /mcp inside a session to complete the sign-in.

Microsoft Copilot

A first-party Copilot listing is planned. Meanwhile, MCP-capable Microsoft surfaces can connect manually: Copilot Studio (custom agents): add a new Tool → Model Context Protocol, set the server URL to https://mcp.perform.ai/mcp with OAuth authentication, and sign in with your Perform.AI account. VS Code (GitHub Copilot agent mode): add to your mcp.json:

{
  "servers": {
    "perform-ai": {
      "type": "http",
      "url": "https://mcp.perform.ai/mcp"
    }
  }
}

VS Code handles the sign-in on first use.

Clients without remote-server support

Some MCP clients only launch local servers and can’t connect to a remote URL with OAuth directly. For those, the open-source mcp-remote bridge runs locally, handles the OAuth flow, and presents Perform.AI to the client as a local server. Install it once (recommended, so first connection doesn’t stall on a download):

npm install -g mcp-remote

Then register it in the client’s MCP configuration, for example in a claude_desktop_config.json-style file (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "perform-ai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.perform.ai/mcp"]
    }
  }
}

Save, then fully restart the client (quit, don’t just close the window). The first tool call opens a browser window for the Perform.AI sign-in. Requires Node.js LTS (node --version to check).

Custom applications

The server speaks standard MCP over Streamable HTTP with OAuth 2.1, including metadata discovery and dynamic client registration, so a spec-compliant client needs no pre-registered credentials:

Protected resource metadata: https://mcp.perform.ai/.well-known/oauth-protected-resource/mcp. It names the Perform.AI authorization server. An unauthenticated request returns 401 with a WWW-Authenticate header pointing to this document.
Grant types: authorization_code (with PKCE) and refresh_token

With the official MCP SDKs, point the client at the server URL and let the SDK’s OAuth support drive the flow:

TypeScript

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(
  new URL("https://mcp.perform.ai/mcp")
  // supply an OAuth client provider per the MCP SDK auth documentation
);
const client = new Client({ name: "your-app", version: "1.0.0" });
await client.connect(transport);
const tools = await client.listTools();

Redirect URIs: client registrations must use HTTPS redirect URIs (loopback URIs for desktop clients are always accepted). If your client redirects to a domain Perform.AI doesn’t recognize, users see a consent screen naming the destination before the redirect proceeds. To allowlist your redirect domains, contact your Key Account Manager or cs@perform.ai. Claude Desktop and Claude Code users never see this screen.

Troubleshooting

Symptom	Fix
The client can’t connect at all	Confirm the URL is exactly `https://mcp.perform.ai/mcp`, with the `/mcp` path and no trailing slash.
`401 invalid_token` when calling the server directly	Expected without a completed OAuth flow. Connect through an MCP client rather than raw HTTP.
The sign-in window doesn’t appear	Check pop-up blocking; with the `mcp-remote` bridge, fully quit and restart the client after editing the config.
Connected, but no data	Select an organization first, and note the server only ever shows what your own Perform.AI login can see.
ChatGPT can’t select an organization	On the Perform.AI plugin page, open Tools and check that Select organization is turned on.

​ChatGPT

​Claude

​Microsoft Copilot

​Clients without remote-server support

​Custom applications

​Troubleshooting

ChatGPT

Claude

Microsoft Copilot

Clients without remote-server support

Custom applications

Troubleshooting