Use this file to discover all available pages before exploring further.
The monday.com app wraps the monday.com v2 GraphQL API behind a simple Prisme.ai interface. It can be used either as a Builder app (automations call monday.com instructions directly) or as a remote MCP server consumed by an Knowledges agent — covering boards, items, columns, groups, workspaces, updates, files, webhooks, docs, folders, tags and activity logs.
Boards & Items
Boards, items, subitems, columns and groups with full CRUD
Collaboration
Updates, notifications, webhooks, tags, users and teams
Base URL of the monday.com API (default https://api.monday.com)
Personal API Token
monday.com Personal API Token (v2), stored as a workspace secret
MCP Endpoint
Auto-populated on install — URL of the MCP endpoint for this instance
MCP API Key
Auto-populated on install — signed key used in the mcp-api-key header. Do not modify
MCP Endpoint and MCP API Key are generated automatically by the onInstall flow and are only needed to expose this instance as an MCP server (see the next tab).
Each instruction resolves credentials from the workspace configuration. All IDs are strings (monday.com uses numeric IDs wrapped as strings). Most list operations accept limit and page for pagination, with 25 items per page by default.
The monday.com app ships with a built-in MCP server. Each app instance gets its own signed mcp-api-key that encodes the workspace ID and a credentials lookup URL — the monday.com Personal API Token is never passed through headers and is resolved server-side from the app configuration.
Agents consume MCP servers directly through Agent Creator capabilities. This is the preferred way to expose monday.com to an agent.
1
Create or open a workspace
From the Prisme.ai console, create a new workspace (or open the one that will host the connector).
2
Install the monday.com app
Open the workspace Imports panel, search for monday.com and install it.
3
Configure the credentials
Open the freshly installed app instance settings and fill in the required fields (see the Usage as App tab for the field-by-field reference).
4
Copy the MCP endpoint and API key
Still on the app instance configuration page, copy the values of MCP Endpoint and MCP API Key — both are generated automatically on install.
5
Open Agent Creator
Switch to Agent Creator and open the agent you want to extend.
6
Add a capability
Add a new capability to the agent:
If a dedicated monday.com capability exists — select it and paste the MCP API Key into the mcp-api-key field. The server URL is already wired.
Otherwise — select the generic custom_mcp capability, paste the MCP Endpoint into the Server URL field, then open the Headers field and add an mcp-api-key entry whose value is the MCP API Key copied earlier:
{ "mcp-api-key": "your-mcp-api-key"}
7
Save
The agent now has access to every monday.com tool exposed by the MCP server.
8
Brief the agent in its system prompt
Wiring the capability is not enough — the agent also needs to know the MCP exists and when to reach for it. Add a short paragraph to the agent’s system prompt. Copy-pasteable starter:
You have access to the monday.com MCP server. Use it whenever the user asks about monday.com content — boards, groups, items, sub-items, columns (status, person, date, …), updates, docs or users. Examples: "List the items in the Sprint board grouped by status", "Add an update to the Marketing campaign item", "Move this item to Done", "Create a new task assigned to Alice". Prefer calling MCP tools directly over guessing, and confirm with the user before any destructive action (delete an item, archive a board, change ownership).
Refine the trigger keywords (board names, workspace names, status conventions) so the agent reliably picks up the right intent in your context.
Use this flow to plug the monday.com MCP into an Knowledges agent that does not yet support the native MCP picker.
1
Install the monday.com app
Install and configure the app in the same workspace as your agent (see the Usage as App tab). Once configured, mcpEndpoint and mcpApiKey are auto-populated.
2
Copy the MCP credentials
Open the app instance config and copy the values of MCP Endpoint and MCP API Key.
3
Open your Knowledges project
Navigate to Advanced > Tools.
4
Add an MCP tool
Click Add and select the MCP tab.
5
Fill in the endpoint
Paste the MCP Endpoint URL copied from the app instance.
6
Add the auth header
In the Headers field, add the signed API key:
{ "mcp-api-key": "your-mcp-api-key"}
7
Save
The agent can now list and call monday.com tools through the MCP endpoint.
The signed mcp-api-key encodes the workspace ID and the getConfig webhook URL. The MCP server validates the signature using the central app secret and transparently fetches the monday.com token and base URL from the installed app. Credentials are cached per tenant for 10 minutes.
column_values is a map of column_id → value, with the payload shape depending on the column type (see monday.com API reference). Set create_labels_if_missing: true to auto-create missing status/dropdown labels.
“Complexity budget exceeded” — monday.com rate limits by query complexity, not request count. Large items_page calls can exhaust the budget quickly. Paginate with smaller limit, or fetch fewer columns.“Invalid column value” — The payload shape depends on the column type. Prefer change_simple_column_value for simple types (text, numbers, status) and change_column_value for complex ones (people, dropdown, timeline).“create_labels_if_missing has no effect” — It only applies to status and dropdown columns, and requires the integration to have board-level write access.“Invalid API key” (MCP) — The mcp-api-key header does not match the central app secret. Reinstall the app instance to regenerate a signed key.