n8n
Connect n8n to build, edit, run and debug workflows, manage executions, credentials, tags and data tables, and publish automations.
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.
Paid plan required before this connector 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.
Where to apply: No application. Click Upgrade plan on the trial's n8n API page (or upgrade under Usage and plan), then create the key in Settings, n8n API with Expiration set to Never.
- n8n's trial notice says it limits API access to prevent abuse, and points to support@n8n.io if that blocks your evaluation.
- A self-hosted instance with N8N_PUBLIC_API_DISABLED=true behaves as if gated: the API answers 404 until the variable is removed.
- n8n's docs describe choosing API key scopes as an Enterprise plan option.
- The MCP access token only reaches workflows with Available in MCP switched on, on every plan.
- Setup time
- 5 min
- Auth
- API credentials
- API base URL
- https://YOUR-INSTANCE.app.n8n.cloud/api/v1
- Rate limits
- n8n publishes no fixed limit for its public REST API. The instance-level MCP server allows each caller 100 requests per 5 minutes by default; self-hosted instances can change that with N8N_MCP_SERVER_RATE_LIMIT.
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
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.
Open https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance).
n8n API
Control n8n programmatically using the n8n API
| Label | Created | Expires |
|---|---|---|
| Backup scripteyJhbGciOi**** | Mar 4, 2026 | Never expires |
| CI deployeyJhbGciOi**** | Aug 19, 2026 | Expires on Nov 17, 2026 |
On an n8n Cloud trial this page shows Upgrade to use API instead of a key list. Skip to the MCP step, or upgrade first.
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.
Open https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance).
n8n API
Control n8n programmatically using the n8n API
Older n8n versions may name this option differently. Whatever yours calls it, pick the one that sets no end date.
Copy the API key
n8n shows the full key once, in the API key created successfully dialog. Copy it, then click Done.
Open https://YOUR-INSTANCE.app.n8n.cloud/settings/api (replace YOUR-INSTANCE with your n8n instance).
n8n API
Control n8n programmatically using the n8n API
The key is a long JWT beginning eyJ. Older instances issue keys starting n8n_api_, which work too.
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.
Connect a client
Pick the client you want to connect, then follow the tailored setup steps.
Generating a new token revokes the previous one, so reconnect PopMCP whenever you rotate it.
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.
Connect in PopMCP
Open your workspace, choose n8n in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| n8n URLtext | 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 keysecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
| MCP access token (optional)secret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against n8n immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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
Why: 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
Why: 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
Why: 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
Why: 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
Why: 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
Why: 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
Why: 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.
Reference
- n8n API documentation
- n8n credentials screen:
https://YOUR-INSTANCE.app.n8n.cloud/settings/api(replace YOUR-INSTANCE with your n8n instance) - Connect an AI client
- Access modes and tool catalogs
Google Cloud Storage
Connect Google Cloud Storage to browse buckets, read and upload files, move and restore them, and see who has access. MCP setup for Claude and ChatGPT.
Supabase
Connect Supabase to query and change your database, run migrations, manage users, files and Edge Functions, and check logs and advisors.