Monday.com MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Monday.com MCP Server show me the first 10 boards in my workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Monday.com MCP Server
A Model Context Protocol (MCP) server that provides tools to interact with the Monday.com API. This server enables AI assistants to retrieve board lists, board details, item content, and user information from your Monday.com workspace.
What is MCP?
The Model Context Protocol (MCP) is an open protocol that enables AI applications to connect to external data sources and tools. MCP servers expose tools, resources, and prompts that can be used by AI assistants like Claude to perform actions and access information.
Related MCP server: Monday.com MCP Server
Features
Board Management: Retrieve paginated lists of boards from your Monday.com workspace
Board Details: Get detailed information about specific boards with filtered items
Item Content: Fetch detailed content for specific board items including parsed descriptions
User Information: Retrieve information about the currently authenticated user
Stdio Transport: Uses standard input/output for communication (perfect for local development)
TypeScript: Written in TypeScript for type safety and better developer experience
Zod Validation: Uses Zod for schema validation of tool inputs and outputs
Error Handling: Comprehensive error handling with user-friendly messages
Prerequisites
Node.js (v18 or higher recommended)
npm or yarn
Monday.com account with API access
Monday.com API token
Installation
Clone or download this repository
Install dependencies:
npm installSet up your Monday.com API token as an environment variable:
export MONDAY_API_TOKEN="your_api_token_here"Or create a .env file in the project root:
MONDAY_API_TOKEN=your_api_token_hereGetting Your Monday.com API Token
Log in to your Monday.com account
Click on your avatar in the bottom left corner
Navigate to Administration → API
Generate a new API token or copy an existing one
Copy the token and save it securely
Building
Compile TypeScript to JavaScript:
npm run buildThis will create the compiled JavaScript files in the dist/ directory.
Running the Server
Production Mode
After building, run the compiled server:
npm startDevelopment Mode
Run the server directly with TypeScript (no build step required):
npm run devThe server will start and listen for MCP requests via stdio (standard input/output).
Available Tools
The server exposes four tools to interact with Monday.com:
1. monday_get_board_list
Retrieve a paginated list of boards from your Monday.com workspace.
Parameters:
limit(number, optional): Maximum number of boards to return (default: 10)page(number, optional): Page number for pagination (default: 1)
Returns:
Array of board objects with ID, name, description, item terminology, state, and views
Example Usage:
// Get first 10 boards
{ limit: 10, page: 1 }
// Get 25 boards from page 2
{ limit: 25, page: 2 }2. monday_get_board_details
Retrieve detailed information about a specific board with filtered items (assigned to me and ready to start).
Parameters:
boardId(string, required): The ID of the board to retrieve details for
Returns:
Board object with filtered items that match the criteria
Example Usage:
{ boardId: "1234567890" }3. monday_get_board_item_list
Retrieve detailed content for a specific board item including parsed description text.
Parameters:
itemId(string, required): The ID of the item to retrieve content for
Returns:
Item object with id, name, and clean description text (images filtered out)
Example Usage:
{ itemId: "9876543210" }4. monday_get_me
Retrieve information about the currently authenticated Monday.com user.
Parameters:
None
Returns:
User object with profile details (id, name, email, etc.)
Example Usage:
// No parameters needed
{}Project Structure
mat-monday-mcp-server/
├── src/
│ ├── index.ts # Main server implementation
│ ├── types.ts # Type definitions
│ ├── config/
│ │ └── client.ts # Monday.com API client configuration
│ ├── services/
│ │ ├── boards.ts # Board-related API operations
│ │ ├── items.ts # Item-related API operations
│ │ ├── monday.ts # Core Monday.com service
│ │ └── users.ts # User-related API operations
│ ├── tools/
│ │ ├── index.ts # Tool registry
│ │ ├── get-board-list.ts # Board list tool
│ │ ├── get-board-details.ts # Board details tool
│ │ ├── get-board-item-content.ts # Item content tool
│ │ └── get-me.ts # Current user tool
│ └── utils/
│ └── content-parser.ts # Content parsing utilities
├── dist/ # Compiled JavaScript (generated)
├── package.json # Project dependencies and scripts
├── tsconfig.json # TypeScript configuration
├── tsup.config.ts # Build configuration
└── README.md # This fileHow It Works
Architecture
Server Creation: The server is created using
McpServerfrom@modelcontextprotocol/sdkTool Registration: All tools are registered via the central
registerToolsfunctionService Layer: Business logic is separated into service modules (boards, items, users)
Monday.com Client: API interactions use the official
@mondaydotcomorg/apiSDKTransport Setup: The server connects via
StdioServerTransportfor stdio communicationRequest Handling: When a client calls a tool, it executes the corresponding service function
Services
Board Service (services/boards.ts)
getBoardListPaginated(limit, page): Fetches a paginated list of boardsgetBoardDetailsPaginated(boardId): Fetches board details with filtered items
Item Service (services/items.ts)
getBoardItemContent(itemId): Fetches item content with parsed description
User Service (services/users.ts)
getMe(): Fetches current authenticated user information
Content Parsing
The server includes utilities to parse Monday.com's description format:
Extracts clean text from Quill-like deltaFormat structures
Filters out image blocks
Provides readable text content
Using with MCP Clients
To use this server with an MCP client (like Claude Desktop or Cursor), you'll need to configure it in your MCP client settings. The server communicates via stdio, so the client needs to spawn the server process.
Example Client Configuration
For Claude Desktop, add to your ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"monday": {
"command": "node",
"args": ["/path/to/mat-monday-mcp-server/dist/index.js"],
"env": {
"MONDAY_API_TOKEN": "your_api_token_here"
}
}
}
}For Cursor, add to your ~/.cursor/mcp.json:
{
"mcpServers": {
"monday": {
"command": "node",
"args": ["/path/to/mat-monday-mcp-server/dist/index.js"],
"env": {
"MONDAY_API_TOKEN": "your_api_token_here"
}
}
}
}Development
Scripts
npm run build- Compile TypeScript to JavaScript using tsupnpm start- Run the compiled servernpm run dev- Run the server directly with TypeScript (development mode)
Dependencies
@modelcontextprotocol/sdk- Official MCP SDK for TypeScript/Node.js@mondaydotcomorg/api- Official Monday.com API SDKzod- Schema validation librarytypescript- TypeScript compilertsup- TypeScript bundler for building
Adding New Tools
To add a new tool:
Create a new file in
src/tools/(e.g.,my-new-tool.ts)Define a
ToolDefinitionwith name, config, and handlerImport it in
src/tools/index.tsAdd it to the
toolsarray in theregisterToolsfunction
Example:
// src/tools/my-new-tool.ts
import { z } from 'zod'
import type { ToolDefinition } from '../index'
export const myNewTool: ToolDefinition = {
name: 'monday_my_new_tool',
config: {
title: 'My New Tool',
description: 'Description of what this tool does',
inputSchema: {
param: z.string().describe('Description of parameter')
},
outputSchema: {
result: z.any().describe('Result description')
}
},
handler: async (inputs: any) => {
try {
// Tool logic here
return {
content: [{ type: 'text', text: 'Success message' }],
structuredContent: { result: {} }
}
} catch (error) {
const errorMessage = error instanceof Error ? error.message : 'Unknown error'
return {
content: [{ type: 'text', text: `Error: ${errorMessage}` }],
structuredContent: {
result: { error: true, type: 'ErrorType', message: errorMessage }
}
}
}
}
}Error Handling
All tools include comprehensive error handling:
Errors are caught and returned in both human-readable format (
content) and structured format (structuredContent)Error responses include error type and message
Network errors, authentication issues, and API errors are handled gracefully
Learning Resources
License
ISC
Available Tools
4 toolsmonday_get_board_detailsGet Monday.com 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.
Inputs: boardId (required). Returns: result
monday_get_board_item_listGet Monday.com Board Item ContentB
Retrieve detailed content for a specific board item including its ID, name, and parsed description text.
Inputs: itemId (required). Returns: result
monday_get_board_listGet Monday.com 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.
Inputs: limit, page. Returns: result
monday_get_meGet Monday.com Current UserB
Retrieve information about the currently authenticated Monday.com user including profile details.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Read and write Mural workspaces, rooms, templates, murals and widgets from your AI assistant.
Connect AI assistants to JustRoadmap to list, read and update workspaces, roadmaps, lanes and items. OAuth sign-in with read-only or read-and-change access per workspace. No delete tools.
Create and manage MeisterTask projects, tasks, and notes from your AI assistant.
AI agents use CalmBoard MCP to access board data, tasks, insights, and project workflows.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables MCP clients to interact with Monday.com boards, allowing creation and management of items, sub-items, comments, and retrieval of board information.2134MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Monday.com boards, items, groups, updates, and documents through natural language. Supports creating and managing boards, items, sub-items, comments, and documents with full CRUD operations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Trello boards, cards, lists, and more through a standardized interface.Reciprocal Public 1.5
- AlicenseNot gradedqualityDmaintenanceEnables LLM assistants to query Monday.com boards, groups, items, and columns via a cached SQLite-backed sync engine, minimizing API calls.MIT