Add monday.com MCP server setup page#423
Closed
socialyadept wants to merge 2 commits into
Closed
Conversation
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>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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>
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
monday.com has two ways C1 can govern it, but there was no docs page for either yet. This adds a brand-new setup page with the same two-tab pattern used for the other vendors that ship both a native hosted MCP server and a C1-hosted API-backed MCP server:
mcp.monday.com). Authentication is per-user OAuth with dynamic client registration (DCR) only — monday.com's hosted server doesn't offer a bearer token or API key mode, so there's nothing to create in monday.com first. Listed as plain Monday in the MCP server catalog. Before anyone can connect, an account admin also needs to turn on hosted MCP access under monday.com's own Admin > Permissions > AI Connectors panel.A comparison table above the tabs explains the difference up front (who hosts the server, authentication, access scoping, tool surface, setup effort), and the intro prose is explicit about which catalog entry ("Monday" vs "monday.com") each option maps to, since the two names are easy to conflate.
Also adds the new page to site navigation, alphabetically between the Metronome and n8n entries.
Test plan
/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#..., etc.) exist onmainTabs/Tab/Steps/Step/Note) are balanceddocs.jsonis valid JSON and the new entry is the only change to that file🤖 Generated with Claude Code