MCP reference
Connect Claude Code
Add the IMMA AI MCP server to Claude Code from the terminal and verify the connection.
Preview
Preview: the API and MCP server are in private beta; details may change.
Prerequisites
- Claude Code installed and signed in.
- An IMMA AI API key (
imma_live_...) with at leastposts:write,posts:readandaccounts:readscopes.
Steps
- From a terminal, add the server as a Streamable HTTP transport with your key in the
Authorizationheader:
claude mcp add --transport http imma https://api.getimma.com/mcp \
--header "Authorization: Bearer imma_live_xxxxxxxxxxxxxxxxxxxx"
- Choose a scope depending on where you want the server available:
- Default (no flag): local scope, only the current project.
--scope user: available in every project on this machine.--scope project: written to.mcp.jsonand shared with anyone who checks out the project (do not commit your real key this way; use an environment variable reference instead if your team shares the repo).
- Confirm it was added:
claude mcp list
- Inside a Claude Code session, run
/mcpto see live connection status forimma.
Verify it worked
In a Claude Code session, ask:
Call list_accounts and tell me which social accounts are connected.
claude mcp list should show imma as connected, and the agent's reply should describe your connected accounts (or say none are connected yet).
Common errors
| Symptom | Cause | Fix |
|---|---|---|
claude mcp list shows "Failed to connect" | Bad URL, network issue, or invalid key | Re-run claude mcp get imma to see the failure detail, including the HTTP status returned (a 401 means the key is wrong) |
claude mcp list shows "Needs authentication" | The server responded with 401/403 because no header was configured | Confirm the --header "Authorization: Bearer ..." flag was included when you ran claude mcp add; re-add the server if it is missing |
| Server added but no tools show up | API key scopes do not include any tool's required scope | Generate a new key with posts:write, posts:read, accounts:read at minimum |
| Works in one project but not another | Server was added with local (default) scope | Re-add with --scope user to make it available everywhere |