Skip to content

Use AtriumKit in n8n with the MCP Client node

Call AtriumKit’s MCP server from an n8n workflow to list demos, make personalized links or read analytics, signing in with OAuth or an access token.

  • Updated November 15, 2026

n8n’s MCP Client node can call AtriumKit’s MCP server as a step in a workflow. The workflow gets the same tools an AI assistant gets, without an AI step in between: make a personalized link for each new row in a spreadsheet, pull a demo’s analytics into a weekly report, or look up a demo by its title. There’s no AtriumKit node in n8n. The MCP Client node is how you connect.

The MCP server works on every plan. Each tool keeps the plan limits it has in the app.

The server URL:

https://app.atriumkit.com/mcp

To send AtriumKit’s events into n8n instead (new leads, and demos finished and buttons clicked by people who already left their email), use a webhook, on Pro and Team. See Connect Slack, your CRM or a webhook.

Add the node

  1. In your n8n workflow, add an MCP Client node. It’s in n8n 1.122 and later.
  2. Leave Server Transport on HTTP Streamable.
  3. Set MCP Endpoint URL to https://app.atriumkit.com/mcp.
  4. Choose how it signs in under Authentication: MCP OAuth2 (below) or Bearer Auth with an access token.

Sign in with OAuth

  1. Set Authentication to MCP OAuth2.
  2. Next to Credential for MCP OAuth2 API, choose Create new credential.
  3. Set Server URL to https://app.atriumkit.com/mcp. Leave Register Client Automatically on (called Use Dynamic Client Registration before n8n 2.47), and leave Resource URL empty if your n8n has it. n8n finds AtriumKit’s sign-in page and registers itself.
  4. Click Connect (Connect my account in older versions).
  5. On the AtriumKit page that opens, sign in, pick the workspace and what n8n may do, then click Allow access.

n8n then shows under Connected apps on your AI assistants settings page.

AtriumKit only sends the sign-in back to an n8n address that starts with https://, or to n8n running on localhost. If your n8n runs on plain http:// at another address, use an access token instead.

If your n8n admin has turned on client ID metadata documents (N8N_OAUTH_CIMD_ENABLED), n8n asks AtriumKit to read that document from your n8n, so your n8n must be reachable over HTTPS from the internet. If it isn’t, leave that setting off or use an access token.

Sign in with an access token

  1. In AtriumKit, click ⋯ next to your name at the bottom of the sidebar, choose Account settings, then AI assistants.
  2. Under Access tokens, click New token. Give it a Name, choose What it can do, pick when it Expires and enter Your password.
  3. Click Create token and copy it. It won’t be shown again.
  4. In the MCP Client node, set Authentication to Bearer Auth, create a credential and paste the token into Bearer Token.

Run a tool

Under Tool, n8n lists AtriumKit’s tools from the server. Pick one, then fill in its parameters with Input Mode set to Manual, or pass them as one object with JSON. You can use n8n expressions to fill them from earlier steps.

Some tools that fit a workflow:

  • list_demos finds demos by words in the title (query) and returns each one’s id, which the other tools take as demoId.
  • create_personalized_links makes links for a demo, up to 500 at once, one per prospect, and returns each link’s url. It needs the Edit drafts permission and Pro or Team. Values only fill variables the demo uses.
  • get_analytics returns views, completion and, for one demo (demoId), its step funnel, for the last days. It needs Read analytics. On Free it returns view counts only.
  • list_leads returns the people who left their details, newest first. It needs Read leads, which is only included when you tick it.

For example, create_personalized_links in JSON:

{
  "demoId": "d_Ab12Cd34Ef56Gh78",
  "links": [
    { "label": "Sam Lee, Acme", "values": { "first_name": "Sam", "company": "Acme", "domain": "acme.com" } }
  ]
}

The full list of what the tools can and can’t do is in Connect Claude, ChatGPT or Cursor to AtriumKit.

Permissions and limits

  • The workflow acts as you, in one workspace, with the permissions you chose when you connected or made the token. Your role still applies: a viewer can’t edit, whatever was ticked.
  • Edits to a demo land in its draft and its version history, as they do from an AI assistant. Viewers see them once the demo is published again.
  • AI tools, such as rewriting or translating, use your workspace’s AI credits.
  • Each connection or token can make up to 120 requests a minute.
  • To stop a workflow’s access, click Disconnect next to n8n, or Revoke next to the token, on the AI assistants settings page.