Table of contents
Monday.com has spent the last year building out its own AI layer, and its MCP (Model Context Protocol) server is the piece that matters most for anyone automating from outside the UI: a way to point Claude, Cursor, VS Code or any other MCP-compatible client straight at your monday.com workspace and have it read and act on boards, items and updates without opening the app.
Three servers cover this today: monday.com’s own hosted server, a local variant of the same package built for app development, and a mature third-party option. Here’s how they compare, and how to connect any of them.
Official vs apps mode vs third-party: Monday.com’s MCP landscape
| Official (mcp.monday.com/mcp) | monday apps MCP (local, @mondaydotcomorg/monday-api-mcp) | Third-party (sakce/mcp-server-monday) | |
|---|---|---|---|
| Status | Generally available, pre-installed on every account | Generally available, official npm package | Community maintained, ~30 GitHub stars |
| Auth | OAuth 2.0, or a bearer token with a personal API token | Personal API token via MONDAY_TOKEN | API key and workspace name (MONDAY_API_KEY, MONDAY_WORKSPACE_NAME) |
| Setup time | None, already running, just authorise | ~5 minutes via npx | ~5 minutes via uvx or Docker |
| Hosting | monday.com’s own infrastructure, Streamable HTTP | Runs locally via npx | Runs locally via uvx or Docker |
| Tool coverage | ~20 tools across boards, items, columns and updates | Same tools as the Platform MCP by default; app-development tools instead with --mode apps | Board and item management |
| Cost | Free | Free | Free, open source (MIT licence) |
Monday’s own support documentation confirms the hosted server needs no installation: MCP is preinstalled on every monday.com account, and admins just need to check Admin → Permissions → AI Connectors if a client can’t connect. That same server also now accepts a bearer token with a personal API token as an alternative to the OAuth flow, so scripted or headless setups aren’t forced through a browser consent screen.
If you’re building monday.com apps rather than automating boards, the separate monday apps MCP runs the same @mondaydotcomorg/monday-api-mcp package locally. Leave off --mode apps and it behaves as a local Platform MCP for general workspace automation; add --mode apps and it switches entirely to managing apps, versions, features and deployments instead, a separate concern from boards and items.
For a lighter-weight, self-hosted option that doesn’t touch monday’s own package, the third-party sakce/mcp-server-monday is the established alternative, run via uvx or Docker with an API key and workspace name rather than OAuth.
Connecting an AI client to Monday.com’s MCP server
Setting up the official server with Claude, Cursor or Copilot Studio
- In your AI client’s MCP settings, add a new remote server.
- Paste in the server URL:
https://mcp.monday.com/mcp. - Choose OAuth as the authentication method (or a bearer token with a personal API token, if your client supports it) and enable the server.
- Authorise the connection when prompted, and confirm the workspace to grant access to. The same URL and OAuth flow work for Claude, Cursor, VS Code, ChatGPT and Copilot Studio; monday documents each client’s setup individually.
Running the apps MCP or third-party server locally
- For workspace automation or app development, grab a personal API token from your monday.com account. For the third-party server, grab an API key and note your workspace name instead.
- Add the server to your client config. For the apps package:
npx @mondaydotcomorg/monday-api-mcp -t <your_token>for general workspace automation, or append--mode appsto expose the apps-framework tools instead. For the third-party server: run it viauvx mcp-server-mondayor the published Docker image, withMONDAY_API_KEYandMONDAY_WORKSPACE_NAMEset as environment variables. - Restart your client. No hosting or deployment step is needed since both run locally.
What can you do with it once connected?
Once any of these servers is connected, you can ask your AI client to search across boards and items, create and update items and boards, manage columns, dashboards and widgets, fill in forms, and post updates, all in natural language instead of clicking through monday.com’s UI. With the apps MCP in --mode apps, you can also scaffold, deploy and manage monday.com apps directly from your AI assistant.
If you’re evaluating monday.com itself for a marketing team, rather than just its MCP server, see our breakdown of Monday.com alternatives for marketing teams or browse the rest of the marketing MCP landscape in our MCP servers for marketers roundup, including the sibling work-management review of the ClickUp MCP Server.
About Growth Method
Monday.com’s MCP server is a fast way to ask an AI client to read a board or push a status update, but it’s still bound to monday’s own graph of boards, items and columns, with no concept of a campaign, a hypothesis, or a growth goal. Growth Method is the agentic marketing platform for B2B teams: plan, launch, and analyse campaigns with pre-built AI agents that work from your live marketing data, not from a generic work-management board. Connect your stack, including GitHub, PostHog, GA4 and more, once, and both your team and its agents can move campaigns through a structured plan, launch, analyse lifecycle and report on what actually moved the needle.
We are on-track to deliver a 43% increase in inbound leads this year. There is no doubt the adoption of Growth Method is the primary driver behind these results.
Laura Perrott, Colt Technology Services
If your team is automating monday.com boards but still measuring campaigns by hand, get started: first month free, no credit card required.
Frequently asked questions
Does Monday.com have an official MCP server?
Yes. Monday.com’s official MCP server is hosted at mcp.monday.com/mcp, pre-installed on every monday.com account, and authenticates through OAuth 2.0 or a bearer token with a personal API token.
Does Monday.com’s MCP server support API token authentication?
Yes, alongside OAuth. The hosted server accepts either OAuth 2.0 or a bearer token with a personal API token. The separate monday apps MCP (@mondaydotcomorg/monday-api-mcp) always authenticates with a personal API token via MONDAY_TOKEN, and the third-party sakce/mcp-server-monday uses MONDAY_API_KEY plus MONDAY_WORKSPACE_NAME.
What’s the difference between the official MCP server and the monday apps MCP?
The hosted Platform MCP at mcp.monday.com/mcp reads and writes boards, items and updates for everyday workspace automation. The monday apps MCP is the same @mondaydotcomorg/monday-api-mcp package run locally: without —mode apps it behaves like a local version of the Platform MCP, and with —mode apps it switches to managing apps, versions and deployments in the apps framework instead.
What can the Monday.com MCP server do?
Across all three servers, tools cover searching boards and items, creating and updating items and boards, managing columns and dashboards, posting updates and forms, and, for the apps MCP in apps mode, scaffolding and deploying monday.com apps.