monday-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONDAY_API_TOKEN | Yes | Your monday.com personal API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | List boards visible to the configured user, optionally limited to a workspace. |
| get_board_detailsA | Get a board with its groups and columns. Use before creating items or updating columns. |
| list_board_itemsB | List items from a board with cursor pagination. Call get_board_details first. |
| get_itemA | Get an item, including its board, group, column values, and basic metadata. |
| create_itemC | Create an item in a monday.com board, optionally in a group and with initial column values. |
| update_item_nameC | Rename an existing monday.com item. |
| update_item_column_valuesB | Update one or more column values on a monday.com item. Get board details first. |
| move_item_to_groupC | Move an item to another group on the same monday.com board. |
| list_item_updatesC | List updates and replies on a monday.com item. |
| create_updateB | Post an update or reply on a monday.com item. The body supports monday.com HTML formatting. |
| get_current_userA | Get the monday.com user represented by the configured API token. |
| list_users_and_teamsA | Search monday.com users and teams whose names match the supplied text. |
| list_workspacesC | List workspaces visible to the configured monday.com user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
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.
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.
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.
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.