Monday Qi MCP Server

MCP Server for monday.com, enabling MCP clients to interact with Monday.com boards, items, updates, and documents. The monday qi mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• monday-create-item — Creates a new item or sub-item in a Monday.com board
• monday-get-board-groups — Retrieves all groups from a specified Monday.com board
• monday-create-update — Creates a comment/update on a Monday.com item
• monday-list-boards — Lists all available Monday.com boards
• monday-list-items-in-groups — Lists all items in specified groups of a Monday.com board
• monday-list-subitems-in-items — Lists all sub-items for given Monday.com items
• monday-create-board — Creates a new Monday.com board
• monday-create-board-group — Creates a new group in a Monday.com board
• monday-move-item-to-group — Moves a Monday.com item to a different group
• monday-delete-item — Deletes a Monday.com item
• monday-archive-item — Archives a Monday.com item
• monday-get-item-updates — Retrieves updates/comments for a specific item

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 3 environment variables: MONDAY_API_KEY, MONDAY_WORKSPACE_NAME, UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Monday Qi's toolset — monday-create-item, monday-get-board-groups, monday-create-update and 11 more — is a fair guide to whether it matches your workflow. It is maintained by YajieQi123; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Monday Qi.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the monday qi mcp server does with a few real requests.