Monday.com MCP Server Cursor IDE Setup (2026)

How do you set up the monday.com MCP server in Cursor? monday.com publishes an official server two ways: a hosted HTTP endpoint at https://mcp.monday.com/mcp that needs no local process, or the @mondaydotcomorg/monday-api-mcp npm package you run locally with npx and a MONDAY_TOKEN API token. Either way, once connected, Cursor can read and update boards, items, and columns directly from chat — pulling a board's current state before you write code that syncs to it, instead of tabbing over to the monday.com UI to check column names by hand.

monday.com's data model — boards made of items and columns, where a "column" can be a status, a person, a number, or a dozen other types — is easy to get subtly wrong from memory. The MCP connection lets your AI confirm the actual column types and values on a real board before generating an API call or an automation script against it.

What You Can Do With monday.com MCP in Cursor

Prerequisites

Method 1: Hosted Endpoint (No Local Process)

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "monday": {
      "url": "https://mcp.monday.com/mcp"
    }
  }
}

Restart Cursor. Depending on your Cursor version and monday.com account setup, the first tool call either prompts an authorization flow in the browser or expects credentials to already be associated with the connection. This is the lower-maintenance option if your Cursor build handles monday.com's hosted transport cleanly — there's no token sitting in a local config file.

Method 2: Official npm Package with an API Token

Step 1: Get a monday.com API Token

1. In monday.com, click your avatar (bottom left) → Admin or Developers
2. Open the API section and generate a personal API token (or an app-scoped token if your workspace uses monday apps)
3. Copy the token — treat it like a password, since it carries whatever permissions your monday.com user account has

Step 2: Add the Local Server to mcp.json

{
  "mcpServers": {
    "monday-api-mcp": {
      "command": "npx",
      "args": ["@mondaydotcomorg/monday-api-mcp@latest"],
      "env": {
        "MONDAY_TOKEN": "your-monday-api-token-here"
      }
    }
  }
}

The token goes in the env block as MONDAY_TOKEN, the standard pattern for API-key-based servers on this site — unlike LaunchDarkly's CLI-argument approach, this one is a straightforward environment variable.

Step 3: Restart Cursor and Verify

Fully quit and reopen Cursor. In chat, try:

List the boards I have access to in monday.com

or

Show me the items in my "Product Roadmap" board, grouped by status

A response naming real boards or items confirms the connection. If nothing comes back, check that the token belongs to a user with access to at least one board — a valid but board-less token authenticates fine and returns an empty list, which looks like a broken connection but isn't.

Practical Workflows

Sync check before writing integration code

Show me the exact column IDs and types on the "Bugs" board, so I can match them in the webhook handler I'm about to write

Status audit

List every item on the "Sprint Board" where the status column is "Stuck" and it hasn't been updated in over a week

Cross-reference with code

I'm building a Slack notification for new high-priority items on the "Support Tickets" board — show me a real item so I can confirm which columns actually hold priority and requester info

Bulk item creation from a spec

Create 5 new items on the "Q3 Launch" board matching this checklist, with the status column set to "Not Started" for each

Troubleshooting

Hosted endpoint doesn't prompt for authorization
Some Cursor versions expect remote MCP servers to complete OAuth in-browser on first use; others need credentials configured differently depending on how monday.com's endpoint negotiates the connection. If the hosted route doesn't connect cleanly, fall back to Method 2 — the token-based local package is the more predictable path across Cursor versions.

"Unauthorized" or empty responses with a valid-looking token
Confirm the token belongs to a monday.com user who's actually a member of the board or workspace you're querying. monday.com scopes API access to what the token's owning user can see in the UI — a token can be syntactically valid and still return nothing for a board the user was never invited to.

Column values come back as raw IDs instead of readable text
This is normal for certain column types (status, dropdown, people) where the underlying value is an index or ID that maps to a label defined on the board. Ask Cursor to also pull the board's column definitions so it can translate IDs to labels rather than guessing at what a raw value means.

Server works but writes don't show up in the monday.com UI
Double-check you're looking at the same board and workspace the MCP connection is scoped to — API tokens are tied to a specific monday.com account, and if your browser session is logged into a different workspace, a successful write can land somewhere you're not currently looking.

Frequently Asked Questions

Q: Should I use the hosted endpoint or the local npm package?
A: The hosted endpoint at mcp.monday.com is the lower-maintenance option when your Cursor version supports it cleanly — no token to store locally. The local @mondaydotcomorg/monday-api-mcp package with a MONDAY_TOKEN is the more predictable fallback, and gives you a token you can individually revoke without affecting other connections.

Q: What permissions does the API token need?
A: A monday.com API token inherits the permissions of the user who generated it — there's no separate scoping step for the basic personal token. If you want a connection limited to specific boards, look at monday.com's app-level token options rather than relying on a personal token from a broadly-permissioned account.

Q: Can the MCP server create and modify boards, or just items?
A: Both official routes support item- and column-level reads and writes. Board-level operations (creating new boards, changing board structure) depend on the specific tool set exposed by the version you're running — check what's available in your client's tool list before assuming a board-creation prompt will work.

Q: Does this replace monday.com's own automations and integrations?
A: No — MCP gives your AI assistant on-demand read/write access from inside your editor, which is a different use case than monday.com's built-in automation engine that runs continuously in the background. Use MCP for ad hoc queries and updates during a coding session, and monday.com's native automations for anything that needs to run unattended.

Q: I manage multiple monday.com workspaces — can one connection reach all of them?
A: Access depends on what the authenticated account (token owner, or OAuth session for the hosted route) can see across workspaces. If a workspace isn't showing up, it's almost always because that account isn't a member of it, not a limitation of the MCP server itself.

Related Guides

---