Monday

monday.com

Manage monday.com boards, items, groups, columns, and updates via monday.com's official hosted MCP endpoint.

Authentication

This skill uses the monday MCP server only — there is no monday CLI fallback. The server is not bundled in the plugin's .mcp.json (it would always-load for every project and require MONDAY_TOKEN to be set). Instead, register it per folder with claude mcp add, which defaults to local scope:

export MONDAY_TOKEN="your_monday_api_token"   # avatar → Developers → My access tokens
claude mcp add monday --transport http https://mcp.monday.com/mcp --header 'Authorization: Bearer ${MONDAY_TOKEN}'

This connects to monday's hosted endpoint (https://mcp.monday.com/mcp) over native HTTP transport and passes your personal access token as a Bearer header. Single-quote the header so the token stays a runtime ${MONDAY_TOKEN} reference rather than being written into the stored config.

Why hosted + token, not the local server? The local @mondaydotcomorg/monday-api-mcp package depends on isolated-vm, a native addon with no prebuilt binary for current Node versions — it fails to compile on Node 22+/24+/26. The hosted endpoint needs no native build and no mcp-remote bridge, so it works regardless of your Node version.

All tool calls execute as that user and are subject to that user's monday.com permissions. If mcp__monday__* tools are not available (tool not found errors), the server has not been added or MONDAY_TOKEN is unset — inform the user and point them at the claude mcp add command above, then stop.

MCP Tools

Dynamic API tools (mcp__monday__all_monday_api, get_graphql_schema, get_type_details) expose the full GraphQL API but are disabled by default, and the hosted endpoint registered above provides no way to turn them on — an HTTP URL has no server process to pass launch flags to. The only path that exposes them is registering the local stdio server instead, launched with the flag:

claude mcp add monday -- npx -y @mondaydotcomorg/monday-api-mcp -t "$MONDAY_TOKEN" --enable-dynamic-api-tools true

This is subject to the Node caveat above (the local server's isolated-vm dependency fails to build on Node 22+); on a Node version where it cannot build, the dynamic tools are unavailable and skills that want them must run in their documented degraded modes. The dynamic tools are not compatible with read-only mode.

Usage

1. Understand the request — which board, item, or field? If the board or column IDs are unknown, call get_board_schema (or get_board_items_by_name) first to discover them.
2. Resolve before mutating — column values must match the board's column types and IDs; fetch the schema before create_item or change_item_column_values rather than guessing.
3. Execute the appropriate MCP tool.
4. Present results clearly — show item names with their IDs, board name, and the relevant column values.

Important Rules

• Never create, modify, move, or delete boards, items, columns, or updates without explicit user confirmation — these write to live workspace data.
• delete_item and delete_column are permanent — always confirm the exact target (by name and ID) before deleting.
• Always show IDs alongside names when presenting results, so the user can act on the right object.
• Respect permissions — calls run as the token's user; if a call fails with a permission error, report it rather than retrying with a different approach.