Skip to content

Add an n8n MCP tab alongside n8n API on the n8n setup page#420

Closed
socialyadept wants to merge 1 commit into
mainfrom
muhammad.kumail/n8n-mcp-tab
Closed

Add an n8n MCP tab alongside n8n API on the n8n setup page#420
socialyadept wants to merge 1 commit into
mainfrom
muhammad.kumail/n8n-mcp-tab

Conversation

@socialyadept

Copy link
Copy Markdown
Contributor

Summary

n8n ships its own hosted MCP server in addition to the REST API C1 already wraps as an MCP server. This adds a second tab to the n8n setup page so admins can tell the two apart and set up either one:

  • n8n MCP (default tab) — connects to n8n's own hosted MCP server. n8n Cloud only — self-hosted n8n instances can't use this option. Authentication is per-user OAuth 2.1 with dynamic client registration (recommended), or a personal access token as a bearer fallback. Listed as plain n8n in the MCP server catalog.
  • n8n API (existing content, lightly reorganized) — C1's own MCP server that translates n8n's REST API into tools, using a shared API key. Works with either n8n Cloud or self-hosted n8n. Listed as n8n API in the catalog.

The Cloud-vs-self-hosted scope limit is called out at the very top of the intro (not just in the comparison table), since it's the single biggest thing an admin needs to get right for this vendor. The intro/recommendation prose and comparison table are explicit about which catalog entry ("n8n" vs "n8n API") each option maps to. The existing n8n API tab's content is otherwise unchanged aside from wrapping it in a tab and updating its catalog-name references.

All external n8n reference links were checked and are live.

Test plan

  • Verified all external n8n reference links (docs.n8n.io/connect/..., docs.n8n.io/api/authentication/) resolve live
  • Verified internal doc links/anchors (/product/admin/mcp-servers#..., /product/admin/enable-ai-access-management#..., etc.) exist on main
  • Checked MDX component tags (Tabs/Tab/Steps/Step/Note) are balanced
  • Confirmed the page isn't otherwise referenced in docs.json navigation beyond its existing entry

🤖 Generated with Claude Code

Mirrors the Notion two-tab pattern: n8n's own hosted MCP server
(n8n Cloud workspaces only, per-user OAuth with dynamic client
registration or a personal access token) as the default tab, with
the existing self-hosted/Cloud REST API integration as the second tab.

Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
@mintlify

mintlify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟢 Ready View Preview Jul 24, 2026, 10:03 PM

Copy link
Copy Markdown
Contributor Author

Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request.

@socialyadept
socialyadept deleted the muhammad.kumail/n8n-mcp-tab branch July 24, 2026 22:27
@mintlify

mintlify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟡 Building Jul 24, 2026, 10:02 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant