This guide covers how to connect the Convertr MCP server to four supported AI platforms: ChatGPT, the Claude Desktop app, Microsoft Teams / Microsoft 365 Copilot, and Slack.
Before you start
| Item | Details |
|---|---|
| Convertr MCP server URL |
https://<yourdomain>.cvtr.io/ai/mcp — replace <yourdomain> with your Convertr account subdomain. |
| Authentication | OAuth 2.0 (League), handled entirely through a Convertr-hosted login and consent screen. There's no OAuth Client ID or Secret to obtain or enter for ChatGPT or Claude — you simply enter the MCP server URL, and the platform opens Convertr's login page for you. See What the authorization flow looks like below for the actual screens. (Microsoft Teams/Copilot is one exception: Microsoft's federated connector setup requires an app-level OAuth registration in the Teams Developer Portal — see Section 3. Slack similarly requires creating a Slack app first, but uses Dynamic Client Registration rather than a manual Client ID/Secret — see Section 4.) |
| Network | The server must be reachable over the public internet from each vendor's infrastructure (see platform notes below) — it cannot sit behind a VPN-only or IP-restricted network for hosted AI clients. |
| Account access | The Convertr account used to authenticate determines what data the connector can see. Users only see data their own Convertr account has permission to access. |
What the authorization flow looks like
Whichever platform you connect from, starting the connection opens a Convertr-hosted browser flow with three steps. The screens below show Claude Desktop as the example client — ChatGPT and other MCP clients show the same Convertr-hosted screens, with their own app name in the consent step.
1. Login — "Convertr MCP Authorisation: An MCP client is requesting access to your Convertr account." Sign in with your Convertr email/password, or SSO where enabled.
2. Consent — the client identifies itself (e.g. "Claude wants to connect to Convertr via MCP") and lists exactly what it will and won't be able to do: it will be able to use AI Reporting to query reporting data such as lead counts, campaign performance, and analytics on your behalf; it will not be able to edit, delete, or change any data, or access other users' accounts or data. Select Approve Access to continue, or Deny Access to cancel.
3. Success — once approved, a confirmation banner appears ("Your request has been approved. You will now be redirected back to Claude.") and the browser redirects back into the AI tool, where the connector is now active.
Section 1: ChatGPT
ChatGPT connects to custom remote MCP servers through Developer mode, available on Plus, Pro, Business, Enterprise, and Education accounts.
Steps
- In ChatGPT, go to Settings → Security and login and turn on Developer mode.
- Open ChatGPT Plugins (or the + button in the composer) and choose to create a developer-mode app for a remote MCP server.
- Enter the Convertr MCP server URL:
https://<yourdomain>.cvtr.io/ai/mcp. - Choose OAuth as the authentication method. ChatGPT opens the Convertr-hosted login and consent flow described above — no Client ID or Secret is needed.
- The new app appears under Drafts in app settings. Open its details page to review and toggle individual tools on/off.
- In a conversation, open the Plus menu → Developer mode and select the Convertr app to enable it for that conversation.
Developer mode grants full read/write MCP tool access. Convertr MCP v1 only exposes read-only tools, but review each tool's permissions before enabling, and only approve write-style confirmations you understand.
Notes
- Supported transport: SSE and streaming HTTP.
- ChatGPT calls the MCP server from OpenAI's infrastructure, not the user's device — the server must be publicly reachable.
- Use Advanced Data Analysis alongside the connector to turn pulled campaign data into charts/exports.
Section 2: Claude Desktop app
Claude Desktop connects to remote MCP servers via Custom Connectors. Available on Free, Pro, Max, Team, and Enterprise plans (Free is limited to one custom connector). Note this is the remote connector path, distinct from local MCP servers configured via claude_desktop_config.json.
Individual (Pro / Max) setup
- In Claude Desktop, go to Settings → Customize → Connectors.
- Click +, then Add custom connector.
- Enter the Convertr MCP server URL:
https://<yourdomain>.cvtr.io/ai/mcp. Leave "Advanced settings" (OAuth Client ID/Secret) blank — Convertr doesn't require it for this flow. - Click Add, then Connect. This opens the Convertr-hosted login and consent flow shown above: sign in, review what Claude will and won't be able to do, and select Approve Access.
Team / Enterprise setup
An Owner or Primary Owner adds the connector once for the whole org; members then connect individually.
- Owner: go to Organization settings → Connectors, click Add, hover Custom, select Web, and enter the Convertr MCP server URL (Advanced settings can be left blank). Click Add.
- Members: go to Customize → Connectors, find the Convertr connector (labelled "Custom"), and click Connect to authenticate with your own Convertr account via the login/consent flow above.
Once added, enable the connector per conversation via the + button → Connectors, and toggle it on.
Claude connects to the MCP server from Anthropic's cloud infrastructure, not the local machine — even inside the desktop app. If the Convertr MCP endpoint is ever restricted to specific networks, Anthropic's IP ranges must be allowlisted (see Anthropic's published IP address list).
Section 3: Microsoft Teams / Microsoft 365 Copilot
Teams/Copilot access to Convertr MCP is set up as a custom federated connector in the Microsoft 365 admin center. This path requires admin involvement (Global Administrator or AI Administrator role) and is a one-time org-wide setup, after which the connector is available to Copilot users in Teams.
Unlike ChatGPT and Claude, Microsoft's federated connector setup does require a persistent OAuth app registration (Client ID/Secret and endpoints) in the Teams Developer Portal — this is a Microsoft-side requirement, not a Convertr one. Once that one-time admin registration is done, individual Teams/Copilot users still go through the same Convertr-hosted login and consent screens shown above.
Prerequisites
- Global Administrator or AI Administrator role in the Microsoft 365 admin center.
- An appropriate Microsoft Entra admin role (for SSO) and access to the Teams Developer Portal.
- The Convertr MCP server URL and an OAuth 2.0 client ID/secret for this integration (request from Convertr Engineering/IT).
Step 1: Register OAuth in the Teams Developer Portal
- Sign in to the Teams Developer Portal.
- Go to Tools → OAuth Client Registration → + New OAuth connection.
- Enter: a descriptive Name (e.g. "Convertr MCP"), the Client ID and Client secret from Convertr, the Authorization endpoint and Token endpoint Convertr provides for its OAuth2/League implementation, and the required Scopes.
- Enable PKCE if supported (Convertr's League OAuth upgrade includes PKCE).
- Save, and copy the resulting OAuth client registration ID — you'll need it in Step 2.
Step 2: Create the connector in the Microsoft 365 admin center
- Sign in to the Microsoft 365 admin center.
- Go to Copilot → Connectors → Gallery.
- Under Created by your org, select Add on the Create a new connector tile.
- On the Custom connector page, under Connect to MCP server, select Add.
- Enter a Display name (e.g. "Convertr") and the Base URL:
https://<yourdomain>.cvtr.io/ai/mcp. - Enter the OAuth registration ID from Step 1.
- Select Save.
Step 3: Roll out to users
- From Your Connections, select the Convertr connector and choose Staged rollout to pilot with specific users/groups first.
- When ready, select Deploy to all users.
Changes to a connector can take up to 15 minutes to take effect. Once deployed, users interact with Convertr data through natural-language prompts in Copilot/Teams, the same way they'd query native Microsoft 365 data.
Section 4: Slack
Slack access to Convertr MCP is set up using the Slackbot MCP Client — Slack's built-in feature for connecting remote MCP servers to Slackbot via HTTP. Once connected, Slackbot automatically discovers the Convertr MCP server's tools and invokes them based on user prompts. This section follows Slack's own guide: Connecting an MCP server to the Slackbot MCP Client.
The Slackbot MCP Client (the Apps tab under Slackbot, and the Manage option used to attach an MCP server) requires a Business+ or Enterprise+ Slack plan. It is not available on Free, Pro, or standard Business plans.
Prerequisites
- A Slack org on the Business+ or Enterprise+ plan.
- A Slack app to configure the MCP server on (create one at api.slack.com/apps if you don't already have one) — Convertr doesn't need to know anything about this app in advance.
- Permission to install the app to the workspace/org.
- The Convertr MCP server URL:
https://<yourdomain>.cvtr.io/ai/mcp.
Step 1: Add the Convertr MCP server to the Slack app
- Go to your app at api.slack.com/apps (or click Create New App > Blank App if you don't have one yet).
- Provide a meaningful App name & select the Workspace (your organisation workspace) & create the app.
- In the left sidebar under Features, click MCP Servers.
- Fill in the fields: Name — a display name, e.g. "Convertr"; URL — the Convertr MCP server URL,
https://<yourdomain>.cvtr.io/ai/mcp; Auth Type — select Dynamic Client Registration. - Click Save. No additional fields are needed for DCR beyond the URL.
Adding an MCP server via App Settings automatically adds the mcp:connect scope to the app. The saved server appears in the MCP Server Connection Details table — additional servers can be added later via + Add MCP Server.
Step 3: Install the app
- In the app's OAuth & Permissions page, click Install to Workspace — or Install to Organization if this is a Slack Enterprise org and you want the app available across all workspaces without installing it workspace by workspace.
- Authorize the app when prompted.
Step 4: Add the app in Slackbot
- Open a DM with Slackbot.
- Click the Apps button in the Slackbot toolbar.
- On first use, a list of suggested apps appears. Click the + button next to the Convertr app to add it. (Each user can have up to 5 active MCP servers at a time.)
- Because Convertr uses OAuth (DCR), you'll be redirected through the same Convertr-hosted login and consent flow described above — sign in and select Approve Access.
- Once connected, the app appears under Your apps in the Integrations tab, with a Manage button.
Step 5: Verify and use it
- Ask Slackbot a question that maps to a Convertr tool. Slackbot queries the MCP server's tool definitions and lists what's available.
- Click Manage next to the app in the Integrations tab at any time to view its available tools and permissions.
- Try a natural-language prompt, e.g. "Show me recent campaign performance from Convertr." Since this is a third-party tool, Slackbot will ask you to explicitly authorize each tool call (read or write) the first time: Allow once, Always allow, or Deny. Permissions can be reviewed and changed later in the MCP config dialog.
Notes & troubleshooting
- Requires Business+ or Enterprise+ — see the panel above.
- Tools must respond within 60 seconds, or Slackbot aborts the call and shows the user an error.
- If the Convertr app doesn't appear in Slackbot, confirm it has the
mcp:connectbot scope and that the MCP server is saved in the app manifest/App Settings, then reinstall the app. - invalid_client errors: since Convertr uses DCR, Slackbot registers an OAuth client with Convertr the first time the server URL is added. If that registration is ever invalidated on Convertr's side, disconnecting/reconnecting in Slackbot won't force a new registration — Slack reuses the same client ID for the same URL. To force re-registration, edit the MCP server's URL (even temporarily) and save.
- Debug logs for the connection and tool calls are available under Features → MCP Servers → Logs in App Settings (visible to app collaborators).