Connect n8n

Prerequisites

• An n8n instance (cloud or self hosted) with the LangChain / AI Agent nodes available.
• An IMMA AI API key (imma_live_...) with at least posts:write, posts:read and accounts:read scopes.

Steps

1. In an AI Agent workflow, add an MCP Client Tool node and connect its output to your AI Agent node's tools input.
2. In the node, set:
   • Endpoint: https://api.getimma.com/mcp
   • Server Transport: HTTP Streamable (the current, recommended option; Server Sent Events (Deprecated) is legacy)
   • Authentication: Bearer Auth (or Header Auth with header name Authorization). The node's other options are Multiple Headers Auth, MCP OAuth2 and None.
3. Create a credential for the authentication type you chose:
   • Bearer Auth: paste your key as the token value, without the Bearer prefix.
   • Header Auth: header name Authorization, header value Bearer imma_live_xxxxxxxxxxxxxxxxxxxx.
4. Under Tools to Include, choose All to expose every tool your key's scopes allow, or Selected to expose only specific ones (for example, only list_accounts and get_analytics for a read-only workflow).
5. Save and activate the workflow.

Verify it worked

Run the workflow (or test the AI Agent node directly) with a prompt like:

Call list_accounts and tell me which social accounts are connected.

The node execution should show a successful call to imma with a JSON result listing connected accounts.

Common errors

Symptom	Cause	Fix
Node execution fails with a 401	Credential holds the wrong key, or the Bearer prefix was duplicated	Recreate the credential; for the Bearer auth type, paste the raw key only, n8n adds the prefix
No tools appear in the AI Agent	Tools to Include is set to Selected with none chosen, or the credential is not attached	Set to All, or check at least one tool under Selected
Workflow times out on tool calls	Server Sent Events (Deprecated) selected against a server that only serves Streamable HTTP	Switch Server Transport to HTTP Streamable
Works in manual testing but not in production	Workflow was saved but not activated, or credential is only shared with your user	Activate the workflow, and share the credential with the workflow's owner if run by a service account

Official docs

• MCP Client Tool node