WORK MANAGEMENT / monday.com
monday.com Platform MCP
Read and update boards, items and workdocs through the hosted platform integration.
“Hosted monday.com MCP wraps platform GraphQL operations for assistants.”
01 / THE REASONING
Why this made the selection.
- Official hosted integration with documented authentication and account permissions.
- Inspect board schema and column types before creating or updating a selected item.
- monday.com’s pages describe a hosted platform MCP server that executes as the authenticated user and says privilege elevation is not possible.
- The server does not store or log OAuth tokens, and the hosted server does not support the deprecated SSE transport.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- https://developer.monday.com/api-reference/docs/build-on-monday-with-ai
- https://developer.monday.com/api-reference/docs/integrate-with-monday-mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- Publisher docs distinguish hosted Platform MCP from local Apps MCP and document user-scoped actions plus evolving tool schemas.
- The reviewed endpoint is a hosted service; no open-source licence is inferred from linked SDKs or apps.
- monday.com says MCP tool calls run as the authenticated user, scoped to that user’s platform permissions, and that no privilege elevation is possible.
- Users can only reach workspaces, boards, and items they already have access to.
- The server does not store or log OAuth tokens, so the client owns token lifecycle. The hosted server also does not support the SSE transport.
- The hosted Platform MCP and local Apps MCP serve different workflows and can coexist: platform data versus app-development tools.
Not established by this review
- Server startup, authentication, live tool execution and security isolation were not tested.
- Published package/container parity with a source revision and hosted implementation internals were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Connect the hosted endpoint and complete OAuth for the intended account. A personal API bearer token is a documented alternative.
- Inspect tools/list and board/column schemas before issuing mutations. Use the documented API-Version header when pinning the GraphQL version matters.
- For additional OAuth clients follow the dynamic connector/admin approval process rather than assuming every callback is pre-approved.
- Use the hosted OAuth endpoint for boards/items, and only configure the token-based --mode apps server when app development is needed.
Before you start
- An account with the required publisher permissions and a compatible remote MCP client.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"monday": {
"type": "http",
"url": "https://mcp.monday.com/mcp"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://developer.monday.com/api-reference/docs/build-on-monday-with-ai
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports
https://developer.monday.com/api-reference/docs/integrate-with-monday-mcp
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports