Monday.com MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONDAY_API_TOKEN | Yes | Your Monday.com API token for authentication |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| monday_get_board_listC | Retrieve a paginated list of boards from your Monday.com workspace. Returns board information including ID, name, description, item terminology, state, and views. |
| monday_get_board_detailsC | Retrieve detailed information about a specific board including filtered items (assigned to me and ready to start). Returns board information with items that match the specified criteria. |
| monday_get_board_item_listB | Retrieve detailed content for a specific board item including its ID, name, and parsed description text. |
| monday_get_meB | Retrieve information about the currently authenticated Monday.com user including profile details. |
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 4 tools
The tools have distinct purposes targeting different resources: board lists, board details, board items, and user info. However, monday_get_board_details and monday_get_board_item_list could be slightly confused as both retrieve item-level details, though the former focuses on filtered items within a board and the latter on a specific item's content.
All tool names follow a consistent snake_case pattern with the prefix 'monday_get_' followed by a descriptive noun phrase, making them predictable and easy to understand across the set.
With only 4 tools, the set feels thin for a full Monday.com integration, lacking essential operations like create, update, or delete for boards or items, which limits agent workflows in this domain.
The tool surface is severely incomplete for a Monday.com server, covering only read operations (get) and missing core CRUD functionality for boards, items, columns, and updates, which will cause significant agent failures in managing workflows.