Connect Claude Desktop

Custom connectors use an OAuth sign-in. Per Anthropic's support article, they are available on Claude (claude.ai), Cowork and Claude Desktop, on Free, Pro, Max, Team and Enterprise plans, though the Free plan is limited to one custom connector.

Prerequisites

• Claude.ai, Claude Desktop or Cowork, on any plan (Free, Pro, Max, Team or Enterprise). Free is limited to one custom connector total, so remove another one first if you are already at that limit.
• An IMMA AI account with access to the workspace you want to connect.

Menu labels can change; if yours differ, follow the linked official guide.

Steps

Free, Pro or Max (individual account)

1. Open Customize > Connectors, click +, then Add custom connector.
2. Fill in the connector details:
   • Name: IMMA AI
   • URL: https://api.getimma.com/mcp
   • Leave the optional OAuth client ID and secret under Advanced settings blank; IMMA AI does not need them.
3. Click Add, then click Connect to sign in. You are redirected to IMMA AI's OAuth consent screen, which shows the workspace, your profile and the scopes being requested, then back to Claude.
4. Start a new chat and check the tool picker (the "Search and tools" icon below the message box): imma should be listed with its tools.

Team or Enterprise

1. An Owner or Admin adds the connector once for the whole organization: Organization settings > Connectors, click Add, hover Custom, choose Web, enter the URL https://api.getimma.com/mcp, then click Add.
2. Each member then opens Customize > Connectors, finds IMMA AI in the list, and clicks Connect to sign in with their own IMMA AI account.

Verify it worked

Ask Claude:

Call list_accounts and tell me which social accounts are connected.

A working connection returns a short list of connected accounts (or an empty list if none are connected yet, which is still a successful call). If nothing happens, see Common errors below.

Common errors

Symptom	Cause	Fix
imma does not appear in the tool picker	The connector was added but never authorized, or the app needs a restart	Reopen Customize > Connectors, click Connect on IMMA AI, and complete the login
Consent denied or canceled	You closed the consent screen or clicked deny	Click Connect again and complete the login
Token revoked	Access was revoked from IMMA AI's /developers/mcp page, or the connector was disconnected	Reconnect from Customize > Connectors and log in again
Wrong workspace connected	Chose the wrong workspace on IMMA AI's consent screen	Disconnect the connector and reconnect, picking the right workspace this time
Only some tools appear	Your account's scopes for this connector do not cover every tool	See Troubleshooting for which scope each tool needs

Advanced / alternative: mcp-remote bridge with a Bearer key

Claude Desktop can also connect through claude_desktop_config.json using the mcp-remote bridge with a static Bearer API key instead of OAuth. This is mainly useful for a machine or automation account that cannot complete an interactive login, or as a fallback while you are on an older Claude Desktop build without the custom connector OAuth flow.

• Claude Desktop installed.
• An IMMA AI API key (imma_live_...) with at least posts:write, posts:read and accounts:read scopes. Generate one from the dashboard once your workspace is approved.
• Node.js available on your machine (npx), used by the bridge command below.

1. Click the Claude menu in your system's menu bar (not the settings inside the Claude window itself) and select Settings, then open the Developer tab and click Edit Config. This opens claude_desktop_config.json:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add an imma entry under mcpServers, replacing imma_live_xxxxxxxxxxxxxxxxxxxx with your real key:

{
  "mcpServers": {
    "imma": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.getimma.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer imma_live_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Claude Desktop on Windows does not correctly escape spaces inside args, which can mangle a header value with a space in it (such as Authorization: Bearer ...). The mcp-remote project's own README recommends this pattern instead: no space around the : in the --header argument itself, with the actual credential (which does need its space) moved into an env variable, referenced as ${AUTH_HEADER}. This works on macOS too, so it is used here for every platform.

3. Save the file and fully quit and reopen Claude Desktop (not just close the window).
4. Start a new chat and check the tool picker: imma should be listed with its tools.

Symptom	Cause	Fix
imma does not appear in the tool picker	Config file has a JSON syntax error, or Claude Desktop was not fully restarted	Validate the JSON (a trailing comma is the usual culprit), quit Claude Desktop from the menu bar, then reopen it
Tool call fails with a 401	Wrong or expired API key in the --header argument	Generate a new key from the dashboard and update the config
npx: command not found	Node.js is not installed or not on PATH	Install Node.js, then restart Claude Desktop so it picks up the updated PATH

Official docs

• Get started with custom connectors using remote MCP
• Connect to remote MCP servers