Connect Cursor

Prerequisites

• Cursor installed.
• An IMMA AI API key (imma_live_...) with at least posts:write, posts:read and accounts:read scopes.

Steps

1. Open (or create) an mcp.json file:
   • Project only: .cursor/mcp.json at your project root.
   • Every project: ~/.cursor/mcp.json in your home directory.
2. Add an imma entry with the endpoint URL and an Authorization header:

{
  "mcpServers": {
    "imma": {
      "url": "https://api.getimma.com/mcp",
      "headers": {
        "Authorization": "Bearer imma_live_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Prefer not to put the raw key in a file you might commit? Cursor resolves ${env:VAR_NAME} inside headers, so you can reference an environment variable instead:

{
  "mcpServers": {
    "imma": {
      "url": "https://api.getimma.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:IMMA_API_KEY}"
      }
    }
  }
}

3. Open Cursor's Customize sidebar, find imma in the MCP list, and make sure it is toggled on.

Verify it worked

In a Cursor chat, ask:

Call list_accounts and tell me which social accounts are connected.

The imma server should show as connected in the Customize sidebar, and the response should list your connected accounts.

Common errors

Symptom	Cause	Fix
Server shows disabled in the sidebar	It was added but the toggle was never switched on	Toggle it on; disabled servers do not load or appear in chat
Tool call fails with a 401	Wrong key, or ${env:...} variable is not set in the shell Cursor was launched from	Verify the key, or export the environment variable and restart Cursor
mcp.json changes are not picked up	Cursor caches server state until reload	Reopen the Customize sidebar or restart Cursor
Only some tools show up	API key scopes do not cover every tool	See Troubleshooting for the scope each tool needs

Official docs

• Model Context Protocol (MCP)