create_itemLABSCO SUMMARY
Fourteen named tools, and a hatch to the whole API underneath.
The named tools cover the work most people actually do on a board, and when they do not fit, all_monday_api will run the GraphQL — with get_graphql_schema first so the query is written against the real schema rather than guessed. That hatch is off by default for good reason: it is full API access, which is also why it cannot be combined with read-only mode. Decide which of those two you want before connecting, because you cannot have both.
What it is
Monday.com's MCP server, maintained by the monday.com AI team. The hosted service is the recommended path and needs no local install; the repository also ships the server to run yourself, plus an agent toolkit for building your own agents. Its tools map onto the monday.com GraphQL API, so anything done through it can also be done programmatically.
What you get
- Items — create_item, delete_item, get_board_items_by_name to search a board by term, change_item_column_values, move_item_to_group, and create_update to add a comment
- Boards — create_board with its columns, get_board_schema for the columns and groups a board actually has, create_group, create_column and delete_column
- Accounts — list_users_and_teams, by id, by name, or by searching the account
- WorkForms — create_form, and get_form by its token
- Dynamic API tools, which reach the rest of the API surface: all_monday_api generates and executes any GraphQL query or mutation, get_graphql_schema fetches the schema so the model knows what exists, and get_type_details explains a specific type
- Those three are in beta and off by default — start the server with --enable-dynamic-api-tools true to add them, or only to serve them alone and filter the standard tools out
- --read-only restricts the server to retrieval, which is the setting to reach for when a session should not change anything; note that it is incompatible with the dynamic API tools, which need full API access
- A separate Apps Framework tool set for building monday.com apps, and an agent toolkit package for wiring monday.com into your own agents
Requirements
A monday.com account. The hosted server is registered at https://mcp.monday.com/mcp over Streamable HTTP, with https://mcp.monday.com/sse for clients that only speak SSE; it takes a monday.com API token in an Authorization header, and installing the Monday MCP app from the marketplace switches it to OAuth with workspace controls. Running it locally instead needs Node.js v20 or higher and an API token in MONDAY_TOKEN, launched with npx @mondaydotcomorg/monday-api-mcp. --version pins the monday.com API version, and --header passes a custom authorization header.
Setup effort
One command plus a key — npx @mondaydotcomorg/monday-api-mcp@latest, then supply credentials
USE CASES
Filing work into monday.com from where you already are
Read the board's columns and groups, then create the item with the right column values.
Setting up a board for a new process
Create the board with its columns, then add the groups the workflow needs.
Finding the item someone mentioned by name
Search the board by term rather than asking for an id.
Moving work through its stages
Change the column values and move the item to the group that matches its new state.
Collecting information from outside the team
Create a WorkForm and read it back by its token.
Doing something the named tools do not cover
Fetch the GraphQL schema, inspect the type, and run the query — with the beta tools enabled.
Letting an agent look without letting it write
Start the server read-only, and accept that the dynamic API tools are unavailable in that mode.
17 tools
Listed in project docs. Your client may show a different list.
delete_itemget_board_items_by_namecreate_updatechange_item_column_valuesmove_item_to_groupcreate_boardget_board_schemacreate_groupcreate_columndelete_columnlist_users_and_teamscreate_formget_formall_monday_apiget_graphql_schemaget_type_detailsBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- MONDAY_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
npx
npx @mondaydotcomorg/monday-api-mcp@latestHosted endpoint
https://mcp.monday.com/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor — hosted
{
"mcpServers": {
"monday-mcp": {
"url": "https://mcp.monday.com/mcp"
}
}
}Claude Desktop — local, Cursor — local
{
"mcpServers": {
"monday-api-mcp": {
"command": "npx",
"args": [
"@mondaydotcomorg/monday-api-mcp@latest"
],
"env": {
"MONDAY_TOKEN": "<YOUR_MONDAY_TOKEN>"
}
}
}
}Gemini CLI
gemini extensions install https://github.com/mondaycom/mcpGemini CLI — HTTP
gemini mcp add -t http monday https://mcp.monday.com/mcpAny MCP client — auth header
{
"mcpServers": {
"monday-api-mcp-hosted": {
"command": "npx",
"args": [
"-p",
"node@20",
"mcp-remote",
"https://mcp.monday.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR_TOKEN>"
}
}
}
}Values written as ${…} are filled in only by clients that expand variables.