Set up the monday.com MCP Server

Start Set up the monday.com MCP Server with minimal permissions and verified data flow.

Published on 20.09.2026

The monday.com MCP Server connects your AI agent to boards, items, docs, and dashboards in your work-OS workspace. Start with the hosted service to get going without any local installation, and only switch to the local variant if you need deeper customization.

Connect to the hosted server

For most clients, adding the URL https://mcp.monday.com/mcp as an HTTP remote server is enough — for example in Cursor via the MCP settings or in Claude Desktop via server management. On first connection, a browser window opens for the OAuth login with your monday.com account.

Local variant with an API token

If you want to work offline or customize the open-source server, first generate a personal API token in the monday.com developer area under "My access tokens" and add the command npx @mondaydotcomorg/monday-api-mcp@latest together with the MONDAY_TOKEN environment variable to your client configuration.

Scope access sensibly

Since the server, according to the provider, has no fine-grained scope model, the account used should only have access to the boards and workspaces the AI agent actually needs. For test runs, a separate monday.com account with limited permissions is recommended instead of an admin account.

Published on 20.09.2026

Categories

Frequently asked questions

Do I need a paid monday.com plan?

Usually yes. According to the provider, the free entry plan does not include the API access the MCP server relies on. monday.com/pricing shows which plan includes how many API calls per day.

Hosted or local — which should I choose?

For getting started, the hosted service at mcp.monday.com/mcp is the best fit: no installation, automatic updates, OAuth login. The local variant with npx and a personal API token is mainly worthwhile for offline use or custom modifications to the open-source server.

Can I restrict what the AI agent can access?

According to the provider, the server itself has no fine-grained permission model; once authorized, all tools become accessible. Effective restriction only works through the monday.com board and workspace permissions of the account being used.