Skip to main content
There are two ways to connect Conversion to an AI client. In ChatGPT, Conversion is available as an app: search for it in the app directory and connect it there. Any other MCP-compatible client that supports remote servers can connect by server URL; in Claude, add it as a custom connector.
Conversion is coming soon to Claude’s connector directory, so you’ll be able to find it and connect in a couple of clicks. Until then, add it in Claude manually by URL as described below.
However you add it, you sign in to Conversion and authorize a single business. There’s no API key to create or paste: the MCP server uses OAuth, and your client handles the sign-in for you.

​
Prerequisites

  • A Conversion account with access to at least one business.
  • An MCP-compatible client that supports remote servers, such as Claude, ChatGPT, or Cursor.

​
Connect from ChatGPT

Conversion is available in ChatGPT’s app directory, so there’s nothing to add manually.
  1. Go to Apps and search for Conversion.
  2. Select Conversion and choose Connect, then complete the sign-in and authorization flow (see Signing in).
  3. In a conversation, bring the app in from the Tools menu (the + near the composer → More), or type @Conversion followed by your request.
On Business and Enterprise plans, a workspace admin may need to enable the app before members can connect it.

​
Connect from Claude

Conversion is coming soon to Claude’s connector directory. Until it’s listed, add it as a custom connector by URL.
  1. Go to Settings → Connectors at claude.ai, or open the + menu in the message box (or type /), hover Connectors, and choose Manage connectors.
  2. Choose Add custom connector, name it Conversion, and paste https://mcp.conversion.ai/mcp.
  3. Click Add, then follow the sign-in prompts (see Signing in).
  4. Back in a chat, open the + menu, hover Connectors, and toggle on Conversion. Claude uses it when your request calls for it.
Connectors are available on Claude Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector).

​
Add the server URL in other clients

Any client that supports remote MCP servers can connect by URL, for example Cursor. The server is at: 
https://mcp.conversion.ai/mcp

{
  "mcpServers": {
    "conversion": {
      "url": "https://mcp.conversion.ai/mcp"
    }
  }
}
Then complete the sign-in below.

​
Signing in

However you add Conversion, the first time your client connects it opens a browser window to authorize the connection:
  1. Sign in to Conversion with your account.
  2. Choose the business you want to connect. If you belong to more than one, you pick a single business here. If you belong to only one, it’s selected for you.
  3. Authorize the client. Conversion confirms you have access to that business, then hands your client back a token.
After that, your client stores the authorization and reuses it on later requests, so you won’t sign in every time.

​
What a connection grants

DetailBehavior
AuthenticationOAuth through your Conversion account. You don’t manage a separate API key; signing in handles it.
Business scopeA single business, chosen at sign-in. The client cannot reach data in your other businesses through that connection.
User scopeYour own user. Actions run as you, within your role and permissions in that business.
ContextConversion exposes tools only. Unlike chat, it doesn’t supply your Universal Business Context to the client; your client is the model and controls its own prompt. See Differences from chat.
Access is authorized through your Conversion account using OAuth. You don’t manage a separate API key for the MCP server. Signing in handles authentication.

​
Connecting more than one business

A single connection maps to one business. To work with another business, connect again and authorize that one. Most clients let you add the same connector or server more than once under different names (for example, conversion-acme and conversion-globex), so you can keep separate connections side by side.

​
Confirmation is up to your client

Conversion’s in-product Allow / Deny approval prompts are part of the Chats interface and don’t appear over MCP. Instead, each tool tells your client whether it only reads data or whether it writes, and your client decides when to ask you to confirm:
  • Claude prompts you to allow a tool when it’s about to run, following your connector permission settings.
  • ChatGPT lets you set how often it checks in per app: for example, Always ask, Ask before making changes, or Ask only before important changes (the default).
Because confirmation is handled by your AI client rather than Conversion, review your client’s settings so you understand when it will take a write action on your workspace without asking. See Differences from chat for details.