Skip to main content
Glama

monday-mcp

A lightweight, independent Model Context Protocol (MCP) server for interacting with the monday.com GraphQL API from MCP-compatible AI assistants and development tools. It exposes a focused set of explicit, validated tools and sends fixed GraphQL operations to monday.com; clients cannot inject arbitrary GraphQL.

What is monday-mcp?

monday-mcp is a lightweight Python MCP server that provides a focused set of tools for common monday.com workflows. It is built around:

  • A standard MCP interface over stdio.

  • Predefined GraphQL operations for users, teams, workspaces, boards, groups, columns, items, and updates.

  • Explicit confirmWrite: true confirmation for every data-changing tool.

  • Straightforward local configuration through the MONDAY_API_TOKEN environment variable.

It is an independent open-source project and is not affiliated with, endorsed by, sponsored by, or maintained by monday.com Ltd.

Related MCP server: issue-tracker-mcp

Features

  • Identify the authenticated user and search users and teams.

  • List workspaces and boards; inspect a board's groups and columns.

  • List board items with cursor pagination; retrieve an item and its updates.

  • Create items, rename them, update their column values, and move them between groups.

  • Post updates and replies.

  • Require confirmWrite: true for every data-changing tool.

  • Keep the API token in the MCP client's environment, not in command-line arguments.

  • Use standard stdio MCP transport.

Architecture

flowchart TD
  A["MCP client or AI assistant"] --> B["monday-mcp (stdio)"]
  B --> C["monday.com GraphQL API"]
  C --> D["monday.com workspace"]

Quick start

git clone https://github.com/<your-account>/monday-mcp.git
cd monday-mcp
uv sync

Create a monday.com personal API token with access to the boards and users you need. Then add this server to an MCP client configuration:

{
  "mcpServers": {
    "monday-mcp": {
      "command": "uv",
      "args": [
        "run",
        "--project",
        "/absolute/path/to/monday-mcp",
        "monday-mcp"
      ],
      "env": {
        "MONDAY_API_TOKEN": "replace_with_your_monday_api_token"
      }
    }
  }
}

Restart or reload the MCP client, then ask it to list your boards, inspect a board, create an item, update its status, or move it to another group. See installation for a complete setup and examples for prompts.

Configuration

MONDAY_API_TOKEN is required. Set it in your MCP client's env configuration; do not commit a real token or pass one on the command line. See configuration.

Documentation

Security

The server reads the token only from MONDAY_API_TOKEN at startup and sends it only as the authorization header for requests to https://api.monday.com/v2. Every tool that creates or modifies data requires confirmWrite: true; grant the token only the access it needs. See SECURITY.md.

Roadmap

Version 1.0.0 supports essential workspace, board, item, user/team, and update workflows. It intentionally does not expose arbitrary GraphQL, board administration, file upload, OAuth, webhooks, or account administration.

Contributing

Contributions are welcome. Read CONTRIBUTING.md before opening a pull request.

Disclaimer

This is an independent open-source project and is not affiliated with, endorsed by, sponsored by, or maintained by monday.com Ltd.

monday.com is a trademark of monday.com Ltd.

License

This project is licensed under the MIT License.

Available Tools

13 tools
create_itemC

Create an item in a monday.com board, optionally in a group and with initial column values.

Inputs: name (required), boardId (required), confirmWrite (required), groupId, +1 more. Returns: result

create_updateB

Post an update or reply on a monday.com item. The body supports monday.com HTML formatting.

Inputs: body (required), confirmWrite (required), itemId, parentUpdateId. Returns: result

get_board_detailsA

Get a board with its groups and columns. Use before creating items or updating columns.

Inputs: boardId (required). Returns: result

get_current_userA

Get the monday.com user represented by the configured API token.

Inputs: no named parameters. Returns: result

get_itemA

Get an item, including its board, group, column values, and basic metadata.

Inputs: itemId (required). Returns: result

list_board_itemsB

List items from a board with cursor pagination. Call get_board_details first.

Inputs: boardId (required), limit, cursor, includeColumnValues. Returns: result

list_boardsA

List boards visible to the configured user, optionally limited to a workspace.

Inputs: page, limit, workspaceId. Returns: result

list_item_updatesC

List updates and replies on a monday.com item.

Inputs: itemId (required), page, limit. Returns: result

list_users_and_teamsA

Search monday.com users and teams whose names match the supplied text.

Inputs: name (required). Returns: result

list_workspacesC

List workspaces visible to the configured monday.com user.

Inputs: page, limit. Returns: result

move_item_to_groupC

Move an item to another group on the same monday.com board.

Inputs: itemId (required), groupId (required), confirmWrite (required). Returns: result

update_item_column_valuesB

Update one or more column values on a monday.com item. Get board details first.

Inputs: itemId (required), boardId (required), columnValues (required), confirmWrite (required), +1 more. Returns: result

update_item_nameC

Rename an existing monday.com item.

Inputs: name (required), itemId (required), boardId (required), confirmWrite (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    All 13 tools have clearly distinct purposes targeting different resources (boards, items, updates, users, workspaces) and actions (list, get, create, update, move). No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_boards, create_item, update_item_column_values). The naming is predictable and uniform.

    Tool Count5/5

    13 tools provide a well-scoped surface for a project management server, covering key operations on boards, items, updates, users, and workspaces without being excessive.

    Completeness3/5

    The tool set covers create, read, and update operations for items and boards, but lacks delete functionality (e.g., delete_item, delete_board) and board creation. Notable gaps in lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers