Add an n8n MCP tab alongside n8n API on the n8n setup page#420
Closed
socialyadept wants to merge 1 commit into
Closed
Add an n8n MCP tab alongside n8n API on the n8n setup page#420socialyadept wants to merge 1 commit into
socialyadept wants to merge 1 commit into
Conversation
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>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
docs.n8n.io/connect/...,docs.n8n.io/api/authentication/) resolve live/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#..., etc.) exist onmainTabs/Tab/Steps/Step/Note) are balanceddocs.jsonnavigation beyond its existing entry🤖 Generated with Claude Code