Monday.com MCP Server
Official monday.com MCP server giving AI agents secure access to monday Work OS boards, items, columns, updates, and forms.
The monday.com MCP server is the official Model Context Protocol implementation maintained by monday.com. It lets AI agents read and act on data inside the monday Work OS, including boards, items, columns, groups, updates, users, and WorkForms. Agents can create new work, search existing items, update column values, post comments, restructure boards, and (in beta) execute arbitrary GraphQL queries against the monday API.
It is offered in two flavors. A hosted remote server is available at https://mcp.monday.com/mcp and is the recommended option for most clients. A local npm package @mondaydotcomorg/monday-api-mcp can be run via npx for users who prefer to self-host or run the server in a CI/CLI workflow. Authentication uses a monday.com API token generated from the account's Developers section, and the agent inherits the permissions of that token.
The server is notable for being first-party (maintained by monday.com itself), for shipping a read-only mode flag for safer agent deployments, and for exposing a Dynamic API Tools mode that lets agents introspect the monday GraphQL schema and run arbitrary queries beyond the prebuilt tools.
Tools
| Tool | Description |
|---|---|
create_item |
Create a new item in a board, optionally inside a specific group. |
delete_item |
Delete an item by ID. |
get_board_items_by_name |
Search items within a board by name. |
create_update |
Post an update/comment on an item. |
change_item_column_values |
Modify one or more column values on an item. |
move_item_to_group |
Move an item from one group to another. |
create_board |
Create a new board, optionally with predefined columns. |
get_board_schema |
Retrieve the structure of a board including groups and columns. |
create_group |
Create a new group inside a board. |
create_column |
Add a new column to a board. |
delete_column |
Remove a column from a board. |
list_users_and_teams |
List users and teams in the monday account. |
create_form |
Create a new WorkForm. |
get_form |
Retrieve an existing WorkForm definition. |
all_monday_api |
Beta: execute an arbitrary GraphQL query against the monday API. |
get_graphql_schema |
Beta: return the monday GraphQL schema for introspection. |
get_type_details |
Beta: get detailed information about a GraphQL type. |
Prerequisites
- A monday.com account with an API token (Profile → Developers → My access tokens)
- For local install: Node.js v20+ and npm v5.2.0+
Option 1: Hosted MCP (recommended)
Point your MCP client at the monday-hosted endpoint:
{
"mcpServers": {
"monday-mcp": {
"url": "https://mcp.monday.com/mcp"
}
}
}
Option 2: Local install via npx
Add to Claude Desktop, Cursor, or any MCP client config:
{
"mcpServers": {
"monday-api-mcp": {
"command": "npx",
"args": ["@mondaydotcomorg/monday-api-mcp@latest"],
"env": {
"MONDAY_TOKEN": "your_monday_api_token"
}
}
}
}
CLI flags
-t, --token: API token (required if not set via env)-v, --version: monday API version-m, --mode: tool set,defaultorapps-ro, --read-only: restrict to read operations-edat, --enable-dynamic-api-tools: enable beta GraphQL tools (all_monday_api,get_graphql_schema,get_type_details)
The agent inherits the permissions of the API token, so scope it to a service account if you need to limit what AI agents can touch.
- Auto-create monday items from emails, Slack messages, or form submissions, populating status, owner, and date columns from the source content.
- Have an agent triage a board: search items by keyword, post comment updates, change status columns, and move stale items to an archive group.
- Generate a new project board with a predefined column schema (status, owner, timeline, priority) at the start of a sprint or client engagement.
- Roll up team workload by listing users and teams, then querying assigned items per person via the dynamic GraphQL tools.
- Read-only reporting: have an agent fetch board schemas and items, then summarize progress or flag overdue work without write permissions.
- "Create a new item called 'Q3 launch retrospective' in the Marketing board, assign it to Sara, and set status to In Progress."
- "Find all items in the Engineering board with 'login' in the title and post an update asking for a status."
- "Create a new board called 'Customer Onboarding' with columns for status, owner, start date, and contract value."
- "List every user on the account and show how many open items each one owns."
- "Move all items in the 'Done' group of the Sales board that closed more than 30 days ago into the Archive group."
- Official, first-party server maintained by monday.com.
- Two deployment modes: hosted remote URL for zero-setup and local npx for self-hosted.
- Read-only mode flag plus token-scoped permissions for safer agent deployments.
- Dynamic API Tools (beta) expose the full monday GraphQL schema for arbitrary queries beyond the prebuilt tools.
- Agent permissions are bound to a single API token, so fine-grained per-tool scoping is limited.
- Some advanced monday features (automations, dashboards, docs) are not surfaced as dedicated tools and require the beta GraphQL escape hatch.
- The dynamic GraphQL tools are still labeled beta and may change.
- sakce/mcp-server-monday: community Python MCP server for monday boards, items, updates, and docs.
- CData monday.com MCP Server: read-only MCP via CData JDBC driver, useful for SQL-style queries.
- Zapier MCP: proxy monday.com actions through Zapier's MCP endpoint, alongside other apps.