# n8n setup for PopMCP You give PopMCP your n8n URL plus an n8n API key, an instance-level MCP access token, or both. Either token works alone; with both you get the full n8n API and n8n's own MCP builder tools. - Auth: API credentials - Setup time: 5 min - API base URL: https://YOUR-INSTANCE.app.n8n.cloud/api/v1 - Credentials screen: https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance) - Provider docs: https://docs.n8n.io/api/authentication/ ## Approval required before this works Only n8n Cloud is gated: n8n switches the public API off during the Cloud free trial, so an n8n API key needs a paid Cloud plan. Self-hosted n8n includes the API, and the instance-level MCP access token works during a trial too. - Typical wait: None. The n8n API page offers Create API key as soon as the Cloud plan is paid. - Cost: n8n's pricing page lists Cloud Starter at €20/month and Pro at €50/month, billed annually. Self-hosted instances are not gated. - Blocked until approved: Every n8n API tool on a Cloud trial: workflows, executions, credentials, tags, variables, projects, data tables and users. The trial's Settings, n8n API page shows Upgrade to use API instead of a key list. - Works meanwhile: Connect with just the n8n URL and an MCP access token from Settings, Instance-level MCP. n8n's own MCP tools (node search, node settings, validation and test runs) work during the trial; add an API key after upgrading. ## Before you begin - An n8n instance PopMCP can reach over public https: n8n Cloud, or a self-hosted n8n behind a domain with a certificate. Local and private-network addresses are refused. - For the n8n API key: a paid n8n Cloud plan or a self-hosted instance. n8n switches the public API off during the Cloud free trial, and a self-hosted instance must not set N8N_PUBLIC_API_DISABLED=true. - An n8n user who is allowed to create API keys. Without that permission n8n disables the Create API key button. - For the optional MCP access token: an n8n version with Settings, Instance-level MCP, and the instance owner or an admin to switch on MCP access. ## Get your credentials ### 1. Open Settings, n8n API Sign in to your n8n, open Settings and click n8n API. On n8n Cloud the address looks like `https://YOUR-INSTANCE.app.n8n.cloud/settings/api`. Screen: https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance) ### 2. Create a key that never expires Click Create API key. Enter a Label such as `PopMCP` and set Expiration to Never so the connection does not lapse. If your plan shows Scopes, choose All for every tool, or Read only for a look-only AI. Click Save. Screen: https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance) ### 3. Copy the API key n8n shows the full key once, in the API key created successfully dialog. Copy it, then click Done. Screen: https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance) ### 4. Optional: turn on instance-level MCP and copy its token Open Settings, Instance-level MCP and click Enable MCP access (owner or admin only). Under Connection details click Connect, switch to the API key tab, and copy the access token, or the whole Configuration JSON. Skip this step if you only want the n8n API tools. ### 5. Fill in the three fields in PopMCP In PopMCP, put the address you open n8n at into n8n URL (any page of your n8n works). Paste the key into n8n API key and, if you made one, the token or Configuration JSON into MCP access token (optional). Click Connect n8n. If the two tokens land in the wrong boxes, PopMCP routes each to the right place. ## Fields PopMCP asks for - n8n URL (instanceUrl) [required]: The address you open n8n at. Copying any page from your browser's address bar works. Self-hosted n8n needs a public https address. - n8n API key (apiKey): In n8n go to Settings, then n8n API, then Create an API key. Set Expiration to Never and copy the key. This covers the full n8n API: workflows, executions, credentials, tags, variables, projects, folders, data tables and users. Not available on n8n Cloud's free trial. - MCP access token (optional) (mcpToken): In n8n go to Settings, then Instance-level MCP, and select Enable MCP access. Then open Connect, switch to the API key tab and copy the token. Adds n8n's own tools for finding nodes, reading their exact settings, validating and testing workflows. ## Verify PopMCP shows n8n as Verified, labelled with your instance host and, when it can read your user, your email, for example `acme.app.n8n.cloud (dana@acme.com)`. Asking the AI to list your workflows returns your real workflow names, and with an MCP token the n8n_mcp_ tools appear too. ## Troubleshooting ### The n8n API page says Upgrade to use API Cause: n8n limits API access during the n8n Cloud free trial. PopMCP reports this as n8n refusing the API key. Fix: Connect with only the n8n URL and an MCP access token for now, or upgrade the Cloud plan and then create the API key. ### n8n rejected the API key Cause: n8n answered 401: the key expired, was deleted, or was copied incompletely. Fix: Create a new key under Settings, n8n API with Expiration set to Never and reconnect. ### No n8n API answered at your URL, or the URL is n8n's website Cause: The n8n URL points at the wrong place (n8n.io, app.n8n.cloud's account portal, or a typo), or a self-hosted instance sets N8N_PUBLIC_API_DISABLED=true. Fix: Copy the address bar while you are inside your n8n (on Cloud it looks like `https://YOUR-INSTANCE.app.n8n.cloud`), and make sure the public API is not disabled. ### PopMCP can only reach n8n on the public internet over https Cause: The URL is localhost, a private IP or plain http, which PopMCP refuses for safety. Fix: Use n8n Cloud, or publish your self-hosted n8n at a public https address through a reverse proxy or tunnel with a certificate. ### MCP access is turned off on this n8n instance Cause: n8n answered 404 `MCP access is disabled`: nobody has switched on instance-level MCP. Fix: Ask the instance owner or an admin to open Settings, Instance-level MCP and click Enable MCP access, then reconnect. ### n8n rejected the MCP access token Cause: Someone generated a new token on the API key tab, which revokes the previous one. Fix: Copy the current token from Settings, Instance-level MCP, Connect, API key and reconnect n8n in PopMCP. ### The AI cannot run or edit a workflow through the n8n_mcp_ tools Cause: n8n's MCP server only exposes workflows with Available in MCP switched on. Fix: In the workflow editor open the workflow menu, choose Settings and turn on Available in MCP, or let the AI use the n8n API tools, which reach every workflow. --- Source: https://www.docs.popmcp.com/docs/integrations/n8n/