Add native MCP tabs alongside API tabs for 10 more vendors#427
Open
socialyadept wants to merge 22 commits into
Open
Add native MCP tabs alongside API tabs for 10 more vendors#427socialyadept wants to merge 22 commits into
socialyadept wants to merge 22 commits into
Conversation
Documents both ways to govern Pylon: C1 registering Pylon's own hosted MCP server (per-user OAuth via dynamic client registration only), and C1's own MCP server translating the Pylon REST API (bearer token only). Follows the two-tab pattern used for other vendors with a native MCP option. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Documents C1 registering Linear's own hosted MCP server as a downstream server, with per-user OAuth (dynamic client registration) as the primary auth method and a personal API key as a bearer-token alternative, matching the two-tab pattern already used for other native MCP integrations. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Lucid now offers its own hosted MCP server (dynamic-client-registration OAuth only), so the Lucid admin page gets the same two-tab pattern as Notion: a native "Lucid MCP" tab (default) plus the existing "Lucid API" tab, each self-contained with its own setup steps and access notes. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
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>
C1 now supports registering GitHub's own hosted MCP server as a downstream server, in addition to the existing C1-hosted GitHub API translation. Add a native GitHub MCP tab (default) documenting OAuth App registration (no dynamic client registration support) and personal-access-token fallback, matching the two-tab pattern already used for other vendors. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Documents the native, Google-hosted Drive MCP server (drivemcp.googleapis.com) as a second tab, matching the Notion two-way pattern: per-user OAuth via a Google Cloud OAuth client (no dynamic client registration), the Drive MCP API enablement step, and Google's fixed MCP tool set. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Documents both ways C1 governs monday.com: the native hosted MCP server (per-user OAuth with dynamic client registration) and C1's own API-backed MCP server (personal API token as a bearer token). Adds the new page to site navigation alongside the other MCP server guides. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Adds a new two-tab MCP server guide for Granola (native hosted MCP server vs. C1's REST API translation), following the existing Notion guide's structure, and adds it to site navigation. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Slack now supports two connection paths, mirroring the Notion MCP pattern: C1's own API-backed MCP server, or Slack's own hosted MCP server registered as a downstream server. Adds the native MCP tab (default) covering the Enable MCP prerequisite, the user-token OAuth flow, and the static-token bearer fallback, alongside the existing API tab. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
PagerDuty now offers its own hosted MCP server, so this adds a second tab documenting that native option (per-user OAuth via a manually registered Scoped OAuth app, since PagerDuty's server doesn't support dynamic client registration, plus an API key / user token fallback), matching the two-tab pattern already used for Notion. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Align monday.mdx's section structure with product/admin/mcp-server/notion.mdx's actual shipped convention (## headings inside each Tab) instead of bold pseudo-headings. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Align pylon.mdx's section structure with product/admin/mcp-server/notion.mdx's actual shipped convention (## headings inside each Tab) instead of bold pseudo-headings. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
…-tab' into muhammad.kumail/native-mcp-tabs-batch
…into muhammad.kumail/native-mcp-tabs-batch
…nto muhammad.kumail/native-mcp-tabs-batch
…o muhammad.kumail/native-mcp-tabs-batch
…b' into muhammad.kumail/native-mcp-tabs-batch
…nto muhammad.kumail/native-mcp-tabs-batch
… into muhammad.kumail/native-mcp-tabs-batch
…into muhammad.kumail/native-mcp-tabs-batch
…' into muhammad.kumail/native-mcp-tabs-batch
This was referenced Jul 24, 2026
4 tasks
Several pages cited the same vendor docs URL multiple times for distinct claims (setup, fallback auth, access scoping, revocation) instead of linking each claim to the specific section it's actually describing. Point each repeated citation at the precise anchor on the target page, verified against the live page's real HTML anchor IDs (not guessed from heading text). Left links bare where the source page has no finer subsection to point to. Also corrects the n8n MCP tab's revoke-access step, which previously described it vaguely — it's Settings > Instance-level MCP > Connected clients > per-client revoke. 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
|
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
1 participant
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
10 more vendors that now ship a native hosted MCP server alongside their existing REST API. Each vendor page gets a two-tab layout — the vendor's native MCP server as the default/first tab, and the existing API-backed option as the second tab — with an intro comparison table explaining the difference (who hosts the server, authentication, access scoping, tool surface, setup effort).
Added a native MCP tab to existing pages:
New two-tab pages (no prior docs page existed) + site navigation entries:
Test plan
/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#..., etc.) confirmed to exist onmainTabs/Tab/Steps/Step/NoteMDX tags balanced on all 10 pagesdocs.jsonis valid JSON; all three new nav entries inserted alphabetically without reformatting surrounding lines##headings inside each tab) matches the convention already shipped on the Notion page🤖 Generated with Claude Code