> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the Monday MCP server

The Monday MCP connector routes your AI agent's tool calls to Monday's own MCP server through Scalekit. Each user signs in to Monday once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 94 tools.

**Authentication:** OAuth 2.1/DCR
**Categories:** Project Management, Collaboration, Productivity
**Tools:** 94: 44 read, 38 write, 12 destructive
**Users sign in with:** OAuth
**OAuth app:** Scalekit's or your own
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=MONDAYMCP)

## What you can do

- **Manage boards and items**: create boards, groups, columns, and items, and update item column values in bulk
- **Search and read workspaces**: search boards, docs, and folders and read board structure, items, and activity
- **Post updates and notify**: comment on items, read updates, and send notifications to users
- **Create docs and forms**: write and edit monday docs, build forms, and submit form responses
- **Automate workflows**: create, list, activate, or delete board automations and plan, build, and publish workflows
- **Analyze board data**: calculate insights across board data and build dashboards and widgets

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Monday MCP connection

   In **AgentKit > Connections**, create a Monday MCP connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

   Scalekit credentials are available for Monday.com, so you don't need to register an OAuth app. To show your own app on the consent screen, use your own credentials instead.

   **Use your own OAuth app:**

   Monday MCP uses Dynamic Client Registration (DCR) with PKCE — no client ID or secret is needed. Scalekit registers the OAuth client automatically the first time a user authorizes the connection, so creating the connection in Scalekit is the only setup step.

   1. ### Create the Monday MCP connection in Scalekit

      In the [Scalekit dashboard](https://app.scalekit.com), go to **AgentKit** > **Connections** > **Create Connection**. Find **Monday MCP** and click **Create**.

      > note: No OAuth app or credentials required
      >
      > Because Monday MCP supports DCR, you do not register an app in the monday.com Developer Center or paste a client ID and secret. Scalekit negotiates the OAuth client with the Monday MCP server at `https://mcp.monday.com/mcp` automatically.

   2. ### Have your user authorize the connection

      Send the user through the connection's authorization link (the magic link Scalekit generates, or the link returned by the SDK). The user signs in to monday.com and grants access.

      On first authorization, Scalekit completes Dynamic Client Registration and PKCE behind the scenes, then stores and refreshes tokens for every user who connects — no further configuration is needed.

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'mondaymcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Monday MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'mondaymcp_allwidgetsschema',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "mondaymcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Monday MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="mondaymcp_allwidgetsschema",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'mondaymcp_agentcatalog',
  toolInput: {
    action: 'list_triggers',
  },
  connector: 'mondaymcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="mondaymcp_agentcatalog",
    tool_input={
        "action": "list_triggers",
    },
    connection_name="mondaymcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `mondaymcp_agentcatalog`

AgentCatalog · Read-only

Browse the account-wide catalog of available trigger types and skills for monday platform agents. READ-ONLY — no agent_id required.

Use this tool to discover what's available BEFORE wiring anything to a specific agent.

ACTIONS:
- list_triggers: { block_reference_ids? } — returns available trigger types.
  Each entry has block_reference_id (required for manage_agent_triggers action:"add"), name, description,
  field_schemas (describes field_values shape), and required_fields (fields to collect from the user).
  Note: only triggers that can be added programmatically appear here. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.)
  require user setup in the monday.com UI and will not appear here.

- list_skills: {} — returns available skills with id, name, description.
  Never guess or invent a skill id — always look it up here before calling manage_agent_skills action:"add".

USAGE EXAMPLES:
- List all trigger types:    { "action": "list_triggers" }
- Fetch specific trigger:    { "action": "list_triggers", "block_reference_ids": ["some-block-ref-id"] }
- List all skills:           { "action": "list_skills" }

RELATED TOOLS:
- manage_agent_triggers — use block_reference_id from list_triggers to attach a trigger to a specific agent
- manage_agent_skills — use skill id from list_skills, or action:"create" to author a new skill, then attach to an agent
- manage_agent — manage the agent entity itself (create, update, delete, activate, etc.)

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `action` (`string`, required): "list_triggers" — fetch available trigger types with block_reference_id, field_schemas, and required_fields. Call before using manage_agent_triggers action:"add". "list_skills" — fetch available skills with id, name, description. Call before using manage_agent_skills action:"add". One of: `list_triggers`, `list_skills`.
- `block_reference_ids` (`array`, optional): Used with action:"list_triggers". Fetch specific trigger types by block_reference_id. Omit to return all trigger types.

Example input: `{"action":"list_triggers"}`

### `mondaymcp_allapiread`

Run read-only Query on the monday.com API · Read-only

Execute read-only GraphQL queries against the monday.com API. Only queries are accepted — mutations are rejected with an error before the request is sent. Use get_graphql_schema and get_type_details tools first to understand the schema before crafting your query.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): Custom GraphQL query/mutation. you need to provide the full query / mutation
- `variables` (`string`, required): JSON string containing the variables for the GraphQL operation

Example input: `{"query":"pricing roadmap","variables":"<variables>"}`

### `mondaymcp_allwidgetsschema`

AllWidgetsSchema · Read-only

Fetch complete JSON Schema 7 definitions for all available widget types in monday.com.

    This tool is essential before creating widgets as it provides:
    - Complete schema definitions for all supported widgets
    - Required and optional fields for each widget type
    - Data type specifications and validation rules
    - Detailed descriptions of widget capabilities

    Use this tool when you need to:
    - Understand widget configuration requirements before creating widgets
    - Validate widget settings against official schemas
    - Plan widget implementations with proper data structures

    The response includes JSON Schema 7 definitions that describe exactly what settings each widget type accepts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mondaymcp_boardinsights`

BoardInsights · Read-only

This tool allows you to calculate insights about board's data by filtering, grouping and aggregating columns. For example, you can get the total number of items in a board, the number of items in each status, the number of items in each column, etc. Use this tool when you need to get a summary of the board's data, for example, you want to know the total number of items in a board, the number of items in each status, the number of items in each column, etc.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper filters and knowing which columns are available.[IMPORTANT]: For some columns, human-friendly label is returned inside 'LABEL_<column_id' field. E.g. for column with id 'status_123' the label is returned inside 'LABEL_status_123' field.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`number`, required): The id of the board to get insights for
- `aggregations` (`array`, optional): The aggregations to get. Before sending the aggregations, read guidelines.aggregation from get_column_type_info with fetchMode "guidelines" for a relevant column type on this board. Transformative functions and plain columns (no function) must be in group by.
- `filters` (`array`, optional): The configuration of filters to apply on the items. Use get_board_info for column ids and types on the board. Before sending the filters, use get_column_type_info with fetchMode "guidelines" and use data.guidelines.filter (null if that type has no documented rules).
- `filtersOperator` (`string`, optional): The operator to use for the filters. One of: `and`, `or`. Default: `and`.
- `groupBy` (`array`, optional): The columns to group by. All columns in the group by must be in the aggregations as well without a function.
- `limit` (`number`, optional): The limit of the results. Default: `1000`.
- `orderBy` (`array`, optional): The columns to order by, will control the order of the items in the response

Example input: `{"boardId":1}`

### `mondaymcp_exploremeetings`

Explore Meetings · Read-only

Discover meetings by topic, or list/browse meetings by date and access. Returns meetings ranked by keyword relevance (matched against title and AI gist — not semantic). USE THIS FIRST for topic/theme questions ("what did we decide about pricing", "find meetings about the acme deal") AND for listing/browsing ("list my recent meetings", "meetings from last week", "my last 10 meetings"). When query is omitted, returns recent meetings filtered by date/access only — this is the tool for listing. Pass returned ids to get_meetings_content for full content, or to search_meetings_content for matching passages. Only indexed meetings are candidates.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `access` (`string`, optional): Filter by access level. OWN: meetings the user participated in or invited the bot to. SHARED_WITH_ME: shared with the user or their team. SHARED_WITH_ACCOUNT: shared with the entire account. ALL: all accessible meetings. Default: OWN. One of: `OWN`, `SHARED_WITH_ME`, `SHARED_WITH_ACCOUNT`, `ALL`. Default: `OWN`.
- `limit` (`integer`, optional): Maximum number of meetings to return (1-20). Keep small - the top-ranked few are usually enough. Default: `10`.
- `query` (`string`, optional): What to look for, matched against each meeting's title and AI gist and ranked by relevance. Omit or leave empty to browse by date/access filters only. Pass the core subject or entity, roughly 1-4 words (e.g. "pricing roadmap" or "acme renewal"), not the full question. Drop instruction words, filler, and synonyms, which dilute the ranking. Default: ``.
- `start_time_from` (`string`, optional): Only include meetings that started at or after this UTC ISO 8601 timestamp (e.g. 2026-07-28T00:00:00Z).
- `start_time_to` (`string`, optional): Only include meetings that started at or before this UTC ISO 8601 timestamp (e.g. 2026-07-28T23:59:59Z).

Example input: `{}`

### `mondaymcp_getaction`

Get Action · Read-only

Retrieve a saved action by ID.

Example:
  id: "550e8400-e29b-41d4-a716-446655440000"

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Action ID

Example input: `{"id":"<id>"}`

### `mondaymcp_getassets`

GetAssets · Read-only

Get assets (files) by their IDs. Returns file metadata including name, extension, size, public URL (valid for 1 hour), thumbnail URL, upload date, and who uploaded it.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ids` (`array`, required): Array of asset IDs to fetch

Example input: `{"ids":[]}`

### `mondaymcp_getautomationruns`

GetAutomationRuns · Read-only

Read automation/workflow run history. Read-only.

Modes:
- "history": paginated run feed (state, duration, error reason). Use "filters" to narrow results and "nextPageOffset" to page (offset-only — next page = previous offset + returned count).
- "detail": single run by "triggerUuid" (required) — returns block steps and MCP tool calls. Set "includeToolEvents": false to skip tool calls.

Scope: provide "boardId" for a specific board or "accountWide": true. One is required.

Known event states: "success", "failure", "exhausted".

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `mode` (`string`, required): history = paginated run feed, detail = single run by triggerUuid. One of: `history`, `detail`.
- `accountWide` (`boolean`, optional): Set true to query account-wide (required if no boardId)
- `blockEventsOffset` (`integer`, optional): detail: block-events page offset
- `boardId` (`string`, optional): Target a specific board by numeric ID
- `filters` (`object`, optional): history: run filters
- `includeToolEvents` (`boolean`, optional): detail: include MCP tool calls (default true)
- `nextPageOffset` (`integer`, optional): history: page offset (offset-only pagination)
- `toolEventsOffset` (`integer`, optional): detail: tool-events page offset
- `triggerUuid` (`string`, optional): detail: required — the run UUID to inspect

Example input: `{"mode":"history"}`

### `mondaymcp_getautomationstatistics`

GetAutomationStatistics · Read-only

Aggregate automation run statistics. Read-only.

Breakdowns:
- "totals": success/failure/total counts at the account or board level.
- "by_entity": per-automation and per-workflow counts for a given "runStatus" (required: "success" | "failure" | "exhausted"). Use "excludeAutomationIds" to omit specific automations.

Scope: provide "boardId" for a specific board or "accountWide": true. One is required.

Optional "userIds" narrows results to specific creators.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `breakdown` (`string`, required): totals = success/failure/total counts, by_entity = per automation/workflow. One of: `totals`, `by_entity`.
- `accountWide` (`boolean`, optional): Set true to query account-wide (required if no boardId)
- `boardId` (`string`, optional): Target a specific board by numeric ID
- `excludeAutomationIds` (`array`, optional): by_entity: automation IDs to exclude from breakdown
- `runStatus` (`string`, optional): by_entity: required run status to break down. One of: `success`, `failure`, `exhausted`.
- `userIds` (`array`, optional): Narrow to specific creator user IDs

Example input: `{"breakdown":"totals"}`

### `mondaymcp_getboardactivity`

GetBoardActivity · Read-only

Get board activity logs for a specified time range (defaults to last 30 days). Optionally filter by item ids or user ids to avoid fetching activity for the entire board.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`number`, required): The id of the board to get activity for
- `fromDate` (`string`, optional): Start date for activity range (ISO8601DateTime format). Defaults to 30 days ago
- `includeData` (`boolean`, optional): Whether to include the raw data payload for each activity entry. The data field contains the full before/after state of changes and can be very large. Only set to true when you need the detailed change data. Default: `false`.
- `itemIds` (`array`, optional): Filter activity to specific item ids. Omit to get activity for the whole board.
- `toDate` (`string`, optional): End date for activity range (ISO8601DateTime format). Defaults to now
- `userIds` (`array`, optional): Filter activity to actions performed by specific user ids.

Example input: `{"boardId":1}`

### `mondaymcp_getboardinfo`

GetBoardInfo · Read-only

Get comprehensive board information including metadata, structure, owners, and configuration. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object. 

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`number`, required): The id of the board to get information for

Example input: `{"boardId":1}`

### `mondaymcp_getboarditemspage`

GetBoardItemsPage · Read-only

Get all items from a monday.com board with pagination support and optional column values and item descriptions. Returns structured JSON with item details, creation/update timestamps, and pagination info. Use the nextCursor parameter from the response to get the next page of results when has_more is true. To retrieve an item description (the rich-text body/details of a monday.com item), set includeItemDescription to true — the response will include the item description document blocks with their content, type, and id. Use this whenever the user asks about an item description, body, details, or notes. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper filters and knowing which columns are available. [REQUIRED PRECONDITION]: For board-relation / cross-board linking tasks, call link_board_items_workflow before using this tool. VIEW-BASED FILTERING: If the user refers to a board view by name (e.g. "show me items in the Overdue view"), first call get_board_info to get the board views, find the matching view by name, then extract its filter field and pass it as the filters argument here.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`number`, required): The id of the board to get items from
- `columnIds` (`array`, optional): The ids of the item columns and subitem columns to get, can be used to reduce the response size when user asks for specific columns. Works only when includeColumns is true. If not provided, all columns will be returned
- `cursor` (`string`, optional): The cursor to get the next page of items, use the nextCursor from the previous response. If the nextCursor was null, it means there are no more items to get
- `filters` (`array`, optional): The configuration of filters to apply on the items. Use get_board_info for column ids and types on the board. Before sending the filters, use get_column_type_info with fetchMode "guidelines" and use data.guidelines.filter (null if that type has no documented rules).
- `filtersOperator` (`string`, optional): The operator to use for the filters. One of: `and`, `or`. Default: `and`.
- `includeColumns` (`boolean`, optional): Whether to include column values in the response.
PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the column data. Excluding columns significantly reduces token usage and improves response latency. If you only need to count items, get item IDs/names, or check if items exist, keep this false. Default: `false`.
- `includeGroup` (`boolean`, optional): Whether to include each item's board group (id and title) in the response. Set to false to reduce token usage when group membership is not needed. Default: `true`.
- `includeItemDescription` (`boolean`, optional): Whether to include the item's description in the response. The item description is the rich-text body content that appears inside a monday.com item (similar to a task description or issue body). Set this to true when the user asks about an item's description, details, body, or notes. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the item description content. Default: `false`.
- `includeSubItems` (`boolean`, optional): Whether to include sub items in the response. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the sub items data. Default: `false`.
- `itemIds` (`array`, optional): The ids of the items to get. The count of items should be less than 100.
- `limit` (`number`, optional): The number of items to get. Default: `25`.
- `orderBy` (`array`, optional): The columns to order by, will control the order of the items in the response
- `searchTerm` (`string`, optional): The search term to use for the search.
    - Use this when: the user provides a vague, incomplete, or approximate search term (e.g., “marketing campaign”, “John’s task”, “budget-related”), and there isn’t a clear exact compare value for a specific field.
    - Do not use this when: the user specifies an exact value that maps directly to a column comparison (e.g., name contains "marketing campaign", status = "Done", priority = "High", owner = "Daniel"). In these cases, prefer structured compare filters.
- `subItemLimit` (`number`, optional): The number of sub items to get per item. This is only used when includeSubItems is true. Default: `25`.

Example input: `{"boardId":1}`

### `mondaymcp_getcolumntypeinfo`

GetColumnTypeInfo · Read-only

Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — use this before creating or updating columns (e.g. create_column) to understand structure, validation rules, and available properties for column settings. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation for building items_page filters and board insights counts (no schema, no GraphQL round-trip). 

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `columnType` (`string`, required): The column type to retrieve information for (e.g., "text", "status", "date", "numbers"). One of: `auto_number`, `board_relation`, `button`, `checkbox`, `color_picker`, `country`, `creation_log`, `date`, `dependency`, `direct_doc`, `doc`, `dropdown`, `email`, `file`, `formula`, `group`, `hour`, `integration`, `item_assignees`, `item_id`, `last_updated`, `link`, `location`, `long_text`, `mirror`, `name`, `numbers`, `people`, `phone`, `progress`, `rating`, `status`, `subtasks`, `tags`, `team`, `text`, `time_tracking`, `timeline`, `unsupported`, `vote`, `week`, `world_clock`.
- `fetchMode` (`string`, optional): fetchMode "schema": JSON settings schema only (GraphQL). fetchMode "guidelines": guidelines.filter and guidelines.aggregation only — no GraphQL round-trip. One of: `schema`, `guidelines`. Default: `schema`.

Example input: `{"columnType":"text"}`

### `mondaymcp_getform`

GetForm · Read-only

Get a monday.com form by its form token. Form tokens can be extracted from the form's url. Given a form url, such as https://forms.monday.com/forms/abc123def456ghi789?r=use1, the formToken is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the formToken is abc123def456ghi789.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `formToken` (`string`, required): No description.

Example input: `{"formToken":"<formToken>"}`

### `mondaymcp_getfullboarddata`

GetFullBoardData · Read-only

INTERNAL USE ONLY - DO NOT CALL THIS TOOL DIRECTLY. This tool is exclusively triggered by UI components and should never be invoked directly by the agent.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`string`, required): The ID of the board to fetch complete data for
- `filters` (`array`, optional): The configuration of filters to apply on the items. Use get_board_info for column ids and types on the board. Before sending the filters, use get_column_type_info with fetchMode "guidelines" and use data.guidelines.filter (null if that type has no documented rules).
- `filtersOperator` (`string`, optional): The operator to use for the filters. One of: `and`, `or`. Default: `and`.

Example input: `{"boardId":"<boardId>"}`

### `mondaymcp_getgraphqlschema`

GetGraphqlSchema · Read-only

Fetch the monday.com GraphQL schema structure including query and mutation definitions. This tool returns available query fields, mutation fields, and a list of GraphQL types in the schema. You can filter results by operation type (read/write) to focus on either queries or mutations.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `operationType` (`string`, optional): Type of operation: "read" for queries, "write" for mutations. One of: `read`, `write`.
- `random_string` (`string`, optional): Dummy parameter for no-parameter tools

Example input: `{}`

### `mondaymcp_getmeetingscontent`

Get Meetings Content · Read-only

Fetch full content (summary, topics, action items, transcript) for meetings you already have ids for. Get those ids from explore_meetings (topic/listing/browse) or search_meetings_content (passages) first — this tool is NOT for discovery or listing. Pass the ids with the include_ flags for the content you need (defaults to the summary if none are set). Requested ids that are not returned are listed in `missing_ids` (not found, not accessible, or no completed recording); meetings whose content was dropped to keep the response within its size limit are listed in `content_omitted_ids`. The search param is a narrow case-insensitive substring fallback on title, participant name, or email — NOT topic/keyword search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `access` (`string`, optional): Filter by access level. OWN: meetings the user participated in or invited the bot to. SHARED_WITH_ME: shared with the user or their team. SHARED_WITH_ACCOUNT: shared with the entire account. ALL: all accessible meetings. Defaults to ALL when fetching specific ids; without ids it excludes meetings shared only account-wide (pass access: ALL to include those). One of: `OWN`, `SHARED_WITH_ME`, `SHARED_WITH_ACCOUNT`, `ALL`.
- `ids` (`array`, optional): The meeting IDs to fetch, from explore_meetings or search_meetings_content. Fetches them in one call.
- `include_action_items` (`boolean`, optional): Include action items for each meeting. Default: `false`.
- `include_summary` (`boolean`, optional): Include the AI-generated summary for each meeting. Default: `false`.
- `include_topics` (`boolean`, optional): Include discussion topics and talking points for each meeting. Default: `false`.
- `include_transcript` (`boolean`, optional): Include the full transcript for each meeting. Transcripts can be very large. Default: `false`.
- `search` (`string`, optional): Narrow fallback only: case-insensitive substring match on title, attendee name, or email. NOT topic/keyword search and NOT for discovery — use explore_meetings to find meetings.

Example input: `{}`

### `mondaymcp_getmondaydevsprintsboards`

GetMondayDevSprintsBoards · Read-only

Discover monday-dev sprints boards and their associated tasks boards in your account.

## Purpose:
Identifies and returns monday-dev sprints board IDs and tasks board IDs that you need to use with other monday-dev tools. 
This tool scans your recently used boards (up to 100) to find valid monday-dev sprint management boards.

## What it Returns:
- Pairs of sprints boards and their corresponding tasks boards
- Board IDs, names, and workspace information for each pair
- The bidirectional relationship between each sprints board and its tasks board

## Note:
Searches recently used boards (up to 100). If none found, ask user to provide board IDs manually.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mondaymcp_getmondayknowledge`

Get Monday Knowledge · Read-only

Ask a question about monday.com and get an AI-generated answer from the official knowledge base.

Use kind="general" for questions about using monday.com — features, automations, UI, help center, and settings. Returns cited source articles with links.
Use kind="developer_docs" for questions about the monday.com API — GraphQL queries and mutations, authentication, rate limits, webhooks, schema, API best practices, and building apps.

Important: do not include PII data in the questions.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `kind` (`string`, required): The knowledge domain to search. Use "developer_docs" for questions about the monday.com API — GraphQL queries and mutations, authentication, rate limits, webhooks, schema, API best practices, and building apps. Use "general" for questions about using monday.com — features, automations, UI, help center, and settings. One of: `developer_docs`, `general`.
- `query` (`string`, required): The question or topic to search for in the monday.com knowledge base.

Example input: `{"kind":"developer_docs","query":"pricing roadmap"}`

### `mondaymcp_getnotetakermeetings`

GetNotetakerMeetings · Read-only

Retrieve notetaker meetings with optional detailed fields. Use include_summary, include_topics, include_action_items, and include_transcript flags to control which details are returned. Use access to filter by meeting access level (OWN, SHARED_WITH_ME, SHARED_WITH_ACCOUNT, ALL). Defaults to OWN. Supports filtering by ids, search term, and cursor-based pagination.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `access` (`string`, optional): Filter meetings by access level. OWN: meetings the user participated in or invited the bot to. SHARED_WITH_ME: meetings shared with the user or their team. SHARED_WITH_ACCOUNT: meetings shared with the entire account. ALL: all meetings the user has access to. One of: `OWN`, `SHARED_WITH_ME`, `SHARED_WITH_ACCOUNT`, `ALL`. Default: `OWN`.
- `cursor` (`string`, optional): Cursor for pagination. Use cursor from the previous page_info to fetch the next page.
- `ids` (`array`, optional): Filter by specific meeting IDs. Use this to fetch one or more specific meetings in a single call.
- `include_action_items` (`boolean`, optional): Whether to include action items for each meeting. Default: `false`.
- `include_summary` (`boolean`, optional): Whether to include the AI-generated summary for each meeting. Default: `false`.
- `include_topics` (`boolean`, optional): Whether to include discussion topics and talking points for each meeting. Default: `false`.
- `include_transcript` (`boolean`, optional): Whether to include the full transcript for each meeting. Transcripts can be very large. Default: `false`.
- `limit` (`number`, optional): Maximum number of notetaker meetings to return per page (1-100). Default: `25`.
- `search` (`string`, optional): Search notetaker meetings by title, participant name, or email.

Example input: `{}`

### `mondaymcp_getsprintsmetadata`

GetSprintsMetadata · Read-only

Get comprehensive sprint metadata from a monday-dev sprints board including:

## Data Retrieved:
A table of sprints with the following information:
- Sprint ID
- Sprint Name
- Sprint timeline (planned from/to dates)
- Sprint completion status (completed/in-progress/planned)
- Sprint start date (actual)
- Sprint end date (actual)
- Sprint activation status
- Sprint summary document object ID

## Parameters:
- **limit**: Number of sprints to retrieve (default: 25, max: 100)

Requires the Main Sprints board ID of the monday-dev containing your sprints.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `sprintsBoardId` (`number`, required): The ID of the monday-dev board containing the sprints
- `limit` (`number`, optional): The number of sprints to retrieve (default: 25, max: 100). Default: `25`.

Example input: `{"sprintsBoardId":1}`

### `mondaymcp_getsprintsummary`

GetSprintSummary · Read-only

Get the complete summary and analysis of a sprint.

## Purpose:
Unlock deep insights into completed sprint performance. 

The sprint summary content including:
- **Scope Management**: Analysis of planned vs. unplanned tasks, scope creep
- **Velocity & Performance**: Individual velocity, task completion rates, workload distribution per team member
- **Task Distribution**: Breakdown of completed tasks by type (Feature, Bug, Tech Debt, Infrastructure, etc.)
- **AI Recommendations**: Action items, process improvements, retrospective focus areas

## Requirements:
- Sprint must be completed and must be created after 1/1/2025 

## Important Note:
When viewing the section "Completed by Assignee", you'll see user IDs in the format "@user-12345678". the 8 digits after the @is the user ID. To retrieve the actual owner names, use the list_users_and_teams tool with the user ID and set includeTeams=false for optimal performance.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `sprintId` (`number`, required): The ID of the sprint to get the summary for (e.g., "9123456789")

Example input: `{"sprintId":1}`

### `mondaymcp_gettypedetails`

GetTypeDetails · Read-only

Get detailed information about a specific GraphQL type from the monday.com API schema

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `typeName` (`string`, required): The name of the GraphQL type to get details for

Example input: `{"typeName":"<typeName>"}`

### `mondaymcp_getupdates`

GetUpdates · Read-only

Get updates (comments/posts) from a monday.com item or board. Specify objectId and objectType (Item or Board) to retrieve updates. For Board queries, you can filter by date range using fromDate and toDate (both required together, ISO8601 format). By default, Board queries return only board discussion. Set includeItemUpdates to true to also include updates on individual items. Returns update text, creator info, timestamps, and optionally replies and assets.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `objectId` (`string`, required): The ID of the item or board to get updates from
- `objectType` (`string`, required): Type of object for which objectId was provided. One of: `Item`, `Board`.
- `fromDate` (`string`, optional): Start of date range filter (e.g. "2025-01-01" or "2025-01-01T00:00:00Z"). Must be used together with toDate. Only supported for Board objectType.
- `includeAssets` (`boolean`, optional): Include file attachments in the response. Default: `false`.
- `includeItemUpdates` (`boolean`, optional): When objectType is Board, also include updates on individual items. Defaults to false, returning only board discussion. Set to true to retrieve all updates on a board, including updates on individual items. Default: `false`.
- `includeReplies` (`boolean`, optional): Include update replies in the response. Default: `false`.
- `limit` (`number`, optional): Number of updates per page (default: 25, max: 100). Default: `25`.
- `page` (`number`, optional): Page number for pagination (default: 1). Default: `1`.
- `toDate` (`string`, optional): End of date range filter (e.g. "2025-06-01" or "2025-06-01T23:59:59Z"). Must be used together with fromDate. Only supported for Board objectType.

Example input: `{"objectId":"<objectId>","objectType":"Item"}`

### `mondaymcp_getusercontext`

GetUserContext · Read-only

Fetch current user information, account information, and their relevant items (boards, folders, workspaces, dashboards).

    Use this tool to:
    - Get context about who the current user is (id, name, title)
    - Get account info: plan tier, active member count, trial status, and active products
    - Get the number of active members in the account (returns active_members_count)
    - Discover user's favorite boards, folders, workspaces, and dashboards
    - Get user's most relevant boards based on visit frequency and recency
    - Get user's most relevant people based on interaction frequency and recency
    - Reduce the need for search requests by knowing user's commonly accessed items

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mondaymcp_invokeprocessplanner`

Process Planner · Read-only

A reasoning-focused process planner with deep knowledge of monday.com workflow architecture. Given a description of a process, it returns a structured textual plan describing one or more related workflows that implement it.

Use this tool for:
- Planning a new workflow or multi-workflow architecture from a process description.
- Deciding whether a process should be implemented as a single workflow or multiple related workflows.
- Producing a concrete, block-level plan (trigger, steps, route keys) that another agent or human can build from.
- Don't tell it about one time actions, like non-repeating resource creations that are needed to set up the process.

This tool does NOT have access to any specific workflow's current state — it plans from scratch using all available blocks. It does not execute any changes.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `prompt` (`string`, required): A description of the process to plan. The planner will design one or more related workflows that implement it, using only the blocks available in the system.

Example input: `{"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager"}`

### `mondaymcp_listactions`

List Actions · Read-only

List all saved actions for the current user.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mondaymcp_listautomations`

ListAutomations · Read-only

List all automations on a specific monday.com board, including their ids, titles, active state, and configuration.
When NOT to use: Do not call this tool to get general board information unrelated to automations.
Note: Some legacy automations may not appear — mention this if users ask about missing automations.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`string`, required): The numeric board ID as a string.
- `cursor` (`string`, optional): Pagination cursor from a previous response. Pass to retrieve the next page of automations.
- `limit` (`integer`, optional): Maximum number of automations to return. Default: 100.

Example input: `{"boardId":"<boardId>"}`

### `mondaymcp_listusersandteams`

ListUsersAndTeams · Read-only

Tool to fetch users and/or teams data. 

      MANDATORY BEST PRACTICES:
      1. ALWAYS use specific IDs or names when available
      2. If no ids available, use name search if possible (USERS ONLY)
      3. Use 'getMe: true' to get current user information
      4. AVOID broad queries (no parameters) - use only as last resort

      REQUIRED PARAMETER PRIORITY (use in this order):
      1. getMe - STANDALONE
      2. userIds
      3. name - STANDALONE (USERS ONLY, NOT for teams)
      4. teamIds + teamsOnly
      5. No parameters - LAST RESORT

      CRITICAL USAGE RULES:
      • userIds + teamIds requires explicit includeTeams: true flag
      • includeTeams: true fetches both users and teams, do not use this to fetch a specific user's teams rather fetch that user by id and you will get their team memberships.
      • name parameter is for USER search ONLY - it cannot be used to search for teams. Use teamIds to fetch specific teams.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `getMe` (`boolean`, optional): [TOP PRIORITY] Use ALWAYS when requesting current user information. Examples of when it should be used: ["get my user" or "get my teams"].
      This parameter CONFLICTS with all others.
- `includeTeamMembers` (`boolean`, optional): Set to true only when you need additional member details for teams other than names and ids.
- `includeTeams` (`boolean`, optional): [AVOID] This fetches all teams in the account. To fetch a specific user's teams just fetch that user by id and you will get their team memberships.
- `name` (`string`, optional): Name-based USER search ONLY. STANDALONE parameter - cannot be combined with others. PREFERRED method for finding users when you know names. Performs fuzzy matching.
      CRITICAL: This parameter searches for USERS ONLY, NOT teams. To search for teams, use teamIds parameter instead.
- `teamIds` (`array`, optional): Specific team IDs to fetch.[IMPORTANT] ALWAYS use when you have team IDs in context, NEVER fetch all teams if specific IDs are available.
      RETURNS: Team details with owners and optional member data.
- `teamsOnly` (`boolean`, optional): Fetch only teams, no users returned. Combine with includeTeamMembers for member details.
- `userIds` (`array`, optional): Specific user IDs to fetch.[IMPORTANT] ALWAYS use when you have user IDs in context. PREFER over general search. RETURNS: user profiles including team memberships

Example input: `{}`

### `mondaymcp_listworkspaces`

ListWorkspaces · Read-only

List all workspaces available to the user, ordered by membership (user's workspaces first). Returns workspaces with their ID, name, and description.
[IMPORTANT] To search for workspaces by name, use the "search" tool with searchType WORKSPACES instead — it provides faster and more accurate results.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`number`, optional): Number of workspaces to return. Default is (100), lower for a smaller response size. Default: `100`.
- `page` (`number`, optional): Page number to return. Default is 1. Default: `1`.

Example input: `{}`

### `mondaymcp_planworkflow`

PlanWorkflow · Read-only

Plans one or more monday.com workflows for a described process using an AI agent.

The agent analyzes the prompt, decides how many workflows are needed, identifies the required boards and columns, selects the correct trigger and action blocks (with their IDs), and returns a structured implementation plan with Mermaid diagrams and build notes for each workflow.

Use this before create_workflow to understand how to break a complex process into individual workflows and which resources to create first.

Parameters:
- prompt: describe the full end-to-end process in plain English. Maximum 2000 characters.

Returns:
- result: structured markdown plan with workflow breakdowns, block IDs, resource definitions, and a list of assumptions and gaps

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `prompt` (`string`, required): Natural-language description of the process to plan. Describe the full end-to-end process in plain English (e.g. "When a deal is marked Won, create a task in the onboarding board and notify the account manager"). The agent will decompose this into one or more monday.com workflows, identify all required boards and columns, and return a structured implementation plan. Maximum 2000 characters.

Example input: `{"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager"}`

### `mondaymcp_readdocs`

ReadDocs · Read-only

Get information about monday.com documents. Supports two modes:

MODE: "content" (default) — Fetch documents with their full markdown content.
- Requires: type ("ids" | "object_ids" | "workspace_ids") and ids array
- Supports pagination via page/limit. Check has_more_pages in response.
- If type "ids" returns no results, automatically retries with object_ids.
- Set include_blocks: true to include block IDs, types, and positions in the response — required before calling update_doc.
- Blocks default to 25 per page. Use blocks_limit and blocks_page to paginate through long documents.
- Set include_comments: true to fetch all comments and replies on the document. Each comment is enriched with anchor info (block_id, selection_from, selection_length) indicating which block and text range it's attached to. Use comments_limit to control how many comments per item (default 50).

MODE: "version_history" — Fetch the edit history of a single document.
- Requires: ids with the document's object_id (use the object_id field from content mode results, NOT the id field).
- The object_id is the numeric ID visible in the document URL.
- Returns restoring points sorted newest-first. Use version_history_limit to cap results (e.g., "last 3 changes" → version_history_limit: 3).
- Use since/until to filter by time range. If omitted, returns full history.
- Set include_diff: true to see what content changed between versions (fetches up to 10 diffs, may be slower).
- Examples:
  - { mode: "version_history", ids: ["5001466606"], version_history_limit: 3 }
  - { mode: "version_history", ids: ["5001466606"], since: "2026-03-11T00:00:00Z", include_diff: true }

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `blocks_limit` (`number`, optional): Maximum number of blocks to return per document (default: 25). Only used in content mode when include_blocks is true.
- `blocks_page` (`number`, optional): Page number for block pagination, starting at 1. Omit to use the API default. Use with blocks_limit to page through documents with more than 25 blocks. Only used in content mode when include_blocks is true.
- `comments_limit` (`number`, optional): Maximum number of comments (updates) to fetch per item when include_comments is true. Defaults to 50. Only used in content mode. Default: `50`.
- `ids` (`array`, optional): Array of ID values. In content mode: matches the query type (ids/object_ids/workspace_ids). In version_history mode: provide the single document object_id here (e.g., ids: ["5001466606"]).
- `include_blocks` (`boolean`, optional): If true, includes the blocks array (block IDs, types, positions, content) in the response. Required when you plan to call update_doc. Defaults to false to reduce response size. Only used in content mode. Default: `false`.
- `include_comments` (`boolean`, optional): If true, fetches all comments and replies on the document. Comments are stored at the item level within the doc backing board. Defaults to false. Only used in content mode. Default: `false`.
- `include_diff` (`boolean`, optional): If true, fetches content diffs between consecutive restoring points. May be slower due to additional API calls. Only used in version_history mode. Default: `false`.
- `limit` (`number`, optional): Number of docs per page (default: 25). Only used in content mode.
- `mode` (`string`, optional): The operation mode. "content" (default) fetches documents with their markdown content. "version_history" fetches the edit history of a single document. One of: `content`, `version_history`. Default: `content`.
- `order_by` (`string`, optional): Order in which to retrieve docs. Only used in content mode. One of: `created_at`, `used_at`.
- `page` (`number`, optional): Page number to return (starts at 1). Only used in content mode.
- `since` (`string`, optional): ISO 8601 date string to filter version history from (e.g., "2026-03-15T00:00:00Z"). If omitted, returns the full history. Only used in version_history mode.
- `type` (`string`, optional): Query type for content mode: "ids", "object_ids", or "workspace_ids". Required when mode is "content". One of: `ids`, `object_ids`, `workspace_ids`.
- `until` (`string`, optional): ISO 8601 date string to filter version history until (e.g., "2026-03-16T23:59:59Z"). Defaults to now. Only used in version_history mode.
- `version_history_limit` (`number`, optional): Maximum number of restoring points to return. Use this when the user asks for "last N changes". Only used in version_history mode.

Example input: `{}`

### `mondaymcp_search`

Search · Read-only

Search within monday.com platform. Can search for boards, documents, folders, workspaces, updates, and items.
For searching/listing specific users and teams, use list_users_and_teams tool.
For account-level info (plan, member count, products), use get_user_context tool.
For groups, use get_board_info tool.
ITEMS search requires a searchTerm and only returns id, title, and url.
WORKSPACES search requires a searchTerm and only returns id, title, and description.
UPDATES search requires a searchTerm and returns id, title (the update body), itemId, boardId, and creatorId. Optionally scope it with boardIds and/or creatorIds.
IMPORTANT: ids returned by this tool are prefixed with the type of the object (e.g doc-123, board-456, folder-789, workspace-101, update-303, item-321). When passing the ids to other tools, you need to remove the prefix and just pass the number.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `searchType` (`string`, required): The type of search to perform. Valid values: BOARD, DOCUMENTS, FOLDERS, WORKSPACES, UPDATES, ITEMS, TIMELINE_ITEMS, DASHBOARDS. One of: `BOARD`, `DOCUMENTS`, `FOLDERS`, `WORKSPACES`, `UPDATES`, `ITEMS`, `TIMELINE_ITEMS`, `DASHBOARDS`.
- `boardIds` (`array`, optional): The ids of the boards to scope the search to. [IMPORTANT] Only applies to UPDATES search, and only pass it if the user explicitly asked to search within specific boards.
- `creatorIds` (`array`, optional): The ids of the users whose updates to search. [IMPORTANT] Only applies to UPDATES search, and only pass it if the user explicitly asked to search updates by specific authors.
- `limit` (`number`, optional): The number of items to get. The max and default value is 20. Default: `20`.
- `searchTerm` (`string`, optional): The search phrase — the text the search matches results against (e.g. a board name, item title, or keywords). Required and must be non-empty. This is NOT a filter or an id — pass the words to look for.
- `workspaceIds` (`array`, optional): The ids of the workspaces to search in. [IMPORTANT] Only pass this param if user explicitly asked to search within specific workspaces.

Example input: `{"searchType":"BOARD"}`

### `mondaymcp_searchmeetingscontent`

Search Meetings Content · Read-only

Search inside meeting content (topics, summary, action items) and return matching passages with their source area. Keyword-ranked (not semantic). When query is omitted, returns content filtered by date/access. Use to find where something was said or decided ("which meeting mentioned the budget freeze", "find the auth migration discussion"). Pass returned ids to get_meetings_content for full context.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `access` (`string`, optional): Filter by access level. OWN: meetings the user participated in or invited the bot to. SHARED_WITH_ME: shared with the user or their team. SHARED_WITH_ACCOUNT: shared with the entire account. ALL: all accessible meetings. Default: OWN. One of: `OWN`, `SHARED_WITH_ME`, `SHARED_WITH_ACCOUNT`, `ALL`. Default: `OWN`.
- `limit` (`integer`, optional): Maximum number of meetings to return (1-15). Content search is heavier, so keep this small. Default: `10`.
- `query` (`string`, optional): The phrase or subject to find inside meeting content. Omit or leave empty to browse content by date/access. Pass the core subject or entity, roughly 1-4 words (e.g. "pricing roadmap" or "acme renewal"), not the full question. Drop instruction words, filler, and synonyms, which dilute the ranking. Default: ``.
- `search_in` (`array`, optional): Which areas of meeting content to search. TOPIC: discussed topics/talking points. SUMMARY: the AI summary. ACTION_ITEM: action items. Defaults to [TOPIC, SUMMARY].
- `start_time_from` (`string`, optional): Only include meetings that started at or after this UTC ISO 8601 timestamp (e.g. 2026-07-28T00:00:00Z).
- `start_time_to` (`string`, optional): Only include meetings that started at or before this UTC ISO 8601 timestamp (e.g. 2026-07-28T23:59:59Z).

Example input: `{}`

### `mondaymcp_showassign`

show-assign · Read-only

[UI COMPONENT] Renders an interactive smart assignment interface visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Helps assign tasks to the right people. Assignment suggestions are based on task details (like name) and person details (such as title, availability, etc).Use for requests to see or use an interactive assignment interface. Always show as much as data possible, while showing the person details like title etc. If you do not have the data available - use the list_users_and_teams tool.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `assignments` (`array`, required): Array of item assignments
- `title` (`string`, required): Board title

Example input: `{"assignments":[],"title":"<title>"}`

### `mondaymcp_showbattery`

show-battery · Read-only

[UI COMPONENT] Renders an interactive battery/progress indicator visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: battery view, progress indicator, status distribution bar, completion percentage visualization, or Monday.com style status breakdown.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`array`, required): Array of segments. Each segment must have 'name' (label), 'y' (value), and 'color' properties.

Example input: `{"data":[]}`

### `mondaymcp_showchart`

show-chart · Read-only

[UI COMPONENT] Renders an interactive chart/graph visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks for: pie chart, bar chart, line graph, data visualization, or any graphical representation of numbers/statistics.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`array`, required): Array of data points. Each point must have 'name' (label) and 'y' (value) properties, with optional 'color' property.
- `type` (`string`, required): Chart type to render: "pie" (circular chart with segments) or "bar" (horizontal bars). One of: `pie`, `bar`.
- `title` (`string`, optional): Optional title text to display above the chart. Leave empty or omit for no title.

Example input: `{"data":[],"type":"pie"}`

### `mondaymcp_showtable`

show-table · Read-only

[UI COMPONENT] Renders an interactive table visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Use when user asks to: display a board as table, show items in table format, view data in tabular layout, or see a Monday.com board visually.
When asked to update an item, use the currently selected item ID (get it from the widget state, using tools like "get_widget_state") for deciding which item to update. 
If no item is selected, ask the user which item should be updated.
After adding an update to an item, you MUST display the table AGAIN, even if the user did not ask you to.

[IMPORTANT][FILTERING PRECONDITION]: IF using filters, you MUST call get_board_info(boardId) FIRST and use the returned boardContextToken.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The ID of the board to display
- `currentlySelectedItemIdForShowingUpdates` (`string`, optional): The ID of the item currently displaying its updates in the expanded view
- `filters` (`array`, optional): The configuration of filters to apply on the items. Before sending the filters, use get_board_info tool to check "filteringGuidelines" key for filtering by the column.
- `filtersOperator` (`string`, optional): The operator to use for the filters. One of: `and`, `or`. Default: `and`.

Example input: `{"boardId":"<boardId>"}`

### `mondaymcp_submitbugorfeaturerequest`

Submit Bug or Feature Request · Read-only

Report a bug, submit a feature request, or share feedback about the monday.com product or this integration.

Call this tool proactively — not just when a user explicitly asks. Use it whenever any of these signals show up:
• A tool produced unexpected errors, empty results, or needed a workaround
• The user tried something monday.com couldn't support and had to settle for a partial or manual solution
• A recurring capability gap is noticed — something requested that simply isn't available in monday.com or this integration
• The user shows repeated frustration (multiple corrections, retrying the same request, "that's wrong again," "why isn't this working")
• A task required multiple retries, an unusually long reasoning chain, or many attempts for something that should've been simple

Parameters:
• title (string, required) — short summary, no PII
• description (string, required) — full details of what happened/expected/requested, no PII
• kind (enum, required) — "bug", "feature_request", or "feedback"
• tool_name (string, optional) — the specific monday.com tool the feedback relates to (e.g. "create_item")

Restriction: Use strictly for things related to monday.com — not for other tools (Google Drive, Slack, GitHub, etc.) that may be in the conversation context. Do NOT include any personally identifiable information (PII) such as names, email addresses, phone numbers, or any other personal data.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `description` (`string`, required): Full details — what happened, what was expected, or what is being requested. Do NOT include any personally identifiable information (PII) such as names, email addresses, phone numbers, or any other personal data.
- `kind` (`string`, required): The kind of submission: general feedback, a feature request, or a bug report. One of: `feedback`, `feature_request`, `bug`.
- `title` (`string`, required): A short summary of the feedback. Do NOT include any personally identifiable information (PII) such as names, email addresses, phone numbers, or any other personal data.
- `tool_name` (`string`, optional): The name of the monday.com MCP tool this feedback is about, if applicable (e.g. "create_item", "get_board_info"). Only include monday.com MCP tool names — do not reference tools from other connected services.

Example input: `{"description":"<description>","kind":"feedback","title":"<title>"}`

### `mondaymcp_validateworkflow`

Validate Workflow · Read-only

Validates the current workflow's structure and step configuration. Reports issues such as a missing trigger or action block, a delay/wait-trigger block left as a leaf, an empty loop, unknown blocks, missing required inputs, type mismatches between a variable and the field it's bound to, cross-branch node-results references, or invalid variable values.

Use this tool when:
- The user asks "is my workflow ready?", "what's missing?", "can I publish?", "validate my workflow", or similar.
- After you finished structural changes, to confirm the user still has things to configure.
- Before suggesting the user publish/activate the workflow.

The tool does NOT modify the workflow. It only inspects the current state. The response is always a JSON object with an "issues" array; an empty array means the workflow is fully configured. Each issue has a "code" discriminator with code-specific fields, and (when applicable) is enriched with stepVisibleId, stepTitle, and blockName for human-readable context.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `workflowObjectId` (`number`, required): The identifier of a workflow object, found in the workflow URL. A workflow object is the entity that is retained across published versions; users can create draft versions related to this workflow object.
- `workflowDraftId` (`number`, optional): The identifier of a draft that belongs to the workflow object referenced by workflowObjectId. When omitted, it refers to the live version of the workflow.

Example input: `{"workflowObjectId":1}`

### `mondaymcp_vibeask`

VibeAsk · Read-only

Ask a read-only question about an existing Vibe app. Blocks for up to 45s (configurable via timeout_ms) awaiting the assistant reply. Status: COMPLETED with the reply, TIMEOUT if the workflow did not finish in time (call vibe_get later to retrieve it), or FAILED if the workflow errored or was cancelled. Optional model to pick the LLM for the answer.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_id` (`integer`, required): Internal Vibe app id
- `prompt` (`string`, required): Question to ask about the app — read-only, no code changes
- `model` (`string`, optional): LLM model for code generation. Omit for automatic selection. Requires model selection enabled for the account. One of: `GEMINI_3_5_FLASH`, `CLAUDE_4_5_SONNET`, `CLAUDE_OPUS_4_6`, `GEMINI_3_7_FLASH`, `CLAUDE_5_SONNET`, `CLAUDE_OPUS_5`.
- `timeout_ms` (`integer`, optional): Maximum time to block waiting for the assistant reply (default 45s)

Example input: `{"app_id":1,"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager"}`

### `mondaymcp_vibeget`

VibeGet · Read-only

Fetch a Vibe app by id. App metadata is always returned, including editor_link — the URL of the Vibe builder/chat page for this app (https://{accountSlug}.monday.com/vibe/app/{appId}); usable as soon as the app row exists. Pass `include` to add expensive slices: status (refreshes status + adds is_busy, default true), messages (with optional from_date), code_versions.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `app_id` (`integer`, required): Internal Vibe app id
- `include` (`object`, optional): Conditional fetch — app metadata is always returned; flags add expensive slices

Example input: `{"app_id":1}`

### `mondaymcp_vibelist`

VibeList · Read-only

List Vibe apps owned by the authenticated user. Supports pagination, search, status, and is_published filters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `is_published` (`boolean`, optional): Filter by publish state
- `limit` (`integer`, optional): Maximum number of apps to return. Default: `20`.
- `page` (`integer`, optional): Page number (1-indexed). Default: `1`.
- `search_term` (`string`, optional): Filter by name (case-insensitive substring match)
- `status` (`string`, optional): Filter by app status. One of: `created`, `generating`, `processing_message`, `deploying`, `ready`.

Example input: `{}`

### `mondaymcp_workspaceinfo`

WorkspaceInfo · Read-only

This tool returns the boards, docs and folders in a workspace and which folder they are in. It returns up to 100 of each object type, if you receive 100 assume there are additional objects of that type in the workspace.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `workspace_id` (`number`, required): The ID of the workspace to get information for

Example input: `{"workspace_id":1}`

### `mondaymcp_changeitemcolumnvalues`

ChangeItemColumnValues · Write

Change the column values of an item in a monday.com board. [REQUIRED PRECONDITION]: For board-relation linking tasks, call link_board_items_workflow before using this tool.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`number`, required): The ID of the board that contains the item to be updated
- `columnValues` (`string`, required): A string containing the new column values for the item following this structure: {\"column_id\": \"value\",... you can change multiple columns at once, note that for status column you must use nested value with 'label' as a key and for date column use 'date' as key} - example: "{\"text_column_id\":\"New text\", \"status_column_id\":{\"label\":\"Done\"}, \"date_column_id\":{\"date\":\"2023-05-25\"}, \"phone_id\":\"123-456-7890\", \"email_id\":\"test@example.com\"}"
- `itemId` (`number`, required): The ID of the item to be updated
- `createLabelsIfMissing` (`boolean`, optional): If true, create missing Status/Dropdown labels when setting those columns. Requires permission to change board structure. Omit or false to only use existing labels.

Example input: `{"boardId":1,"columnValues":"<columnValues>","itemId":1}`

### `mondaymcp_createaction`

Create Action · Write

Save a reusable action (a stored code script). Variables are injected as environment variables (access via os.environ in Python, process.env in JS/TS).

Recommended: Test your code with execute_code before saving to ensure it works correctly.

Network access is restricted to the following hosts: [api.monday.com, mcp.monday.com/mcp]. Requests to any other host will be blocked.

Example:
  name: "Get board items", description: "Fetches items from a board", language: "python", code: "import requests\nprint('done')"

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `code` (`string`, required): Source code (max 1 MB)
- `description` (`string`, required): Short summary: what data the code accesses (specific boards/items by name or ID, or scope if broad), what processing it performs, and how the result is returned. Max 255 characters. Write this well — it is how the action is discovered and reused later.
- `language` (`string`, required): Programming language — one of: javascript, typescript, python. One of: `javascript`, `typescript`, `python`.
- `name` (`string`, required): Short, descriptive action name
- `output_description` (`string`, required): Required. Instructions describing what should be done with the execution output (e.g. "post the summary as an update on item 123"), max 2000 characters. Echoed back in the run_action response.
- `vars_schema` (`array`, optional): Variable definitions — injected as environment variables at execution time

Example input: `{"code":"<code>","description":"<description>","language":"javascript","name":"High Priority Items","output_description":"post the summary as an update on item 123"}`

### `mondaymcp_createautomation`

CreateAutomation · Write

    Creates an automation on a monday board from a structured natural-language description.

Use this tool only when you know:
- boardId
- the user's intended trigger
- at least one intended action
- any details the user provided that are relevant to the trigger, conditions, or actions

The caller does not need to know the exact available automation blocks or their required fields. Describe the user's intent clearly — the tool will translate that intent into supported blocks and values.

If a required detail is missing from the user's request, ask for clarification before calling the tool.

If the tool returns status: "needs_clarification", present the unresolved fields to the user, gather answers, then call the tool again.

Describe the automation in this format:

Trigger:
  When <the event that should start the automation>
  Details:
    <relevant detail>: <value>

Conditions:
  - Only if <condition that should be true>
    Details:
      <relevant detail>: <value>

Actions:
  - <action the automation should perform>:
      <relevant detail>: <value>

Rules:
- Use one trigger.
- Conditions are optional.
- Multiple conditions mean AND.
- Use one or more actions.
- Do not use branching.
- Use natural language, not block IDs or internal field names.
- Actions may reference values from the trigger context, such as "{{item name}}", "{{creator}}", "{{status}}", "{{group}}", or "{{board}}".

Terminology:
- Trigger: the event that starts the automation, such as "when a new item is created".
- Conditions: optional requirements that must be true before actions run.
- Actions: what the automation does when it runs.

Example:

Trigger:
  When a new item is created

Actions:
  - Send a notification:
      Recipient: John Snow
      Title: Important Update
      Message: The item "{{item name}}" was created.

  - Move the item to a group:
      Group: Top group

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The numeric board ID as a string.
- `userPrompt` (`string`, required): Structured description of the automation to create.

Example input: `{"boardId":"<boardId>","userPrompt":"<userPrompt>"}`

### `mondaymcp_createboard`

CreateBoard · Write

Create a monday.com board

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardName` (`string`, required): The name of the board to create
- `boardDescription` (`string`, optional): The description of the board to create
- `boardKind` (`string`, optional): The kind of board to create. One of: `private`, `public`, `share`. Default: `public`.
- `boardOwnerIds` (`array`, optional): Optional list of user IDs to set as board owners
- `workspaceId` (`string`, optional): The ID of the workspace to create the board in

Example input: `{"boardName":"<boardName>"}`

### `mondaymcp_createcolumn`

CreateColumn · Write

Create a new column in a monday.com board

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`number`, required): The id of the board to which the new column will be added
- `columnTitle` (`string`, required): The title of the column to be created
- `columnType` (`string`, required): The type of the column to be created. One of: `auto_number`, `board_relation`, `button`, `checkbox`, `color_picker`, `country`, `creation_log`, `date`, `dependency`, `direct_doc`, `doc`, `dropdown`, `email`, `file`, `formula`, `group`, `hour`, `integration`, `item_assignees`, `item_id`, `last_updated`, `link`, `location`, `long_text`, `mirror`, `name`, `numbers`, `people`, `phone`, `progress`, `rating`, `status`, `subtasks`, `tags`, `team`, `text`, `time_tracking`, `timeline`, `unsupported`, `vote`, `week`, `world_clock`.
- `columnDescription` (`string`, optional): The description of the column to be created
- `columnSettings` (`string`, optional): Column-specific configuration settings as a JSON string. Use get_column_type_info with fetchMode "schema" for the JSON schema for the given column type.

Example input: `{"boardId":1,"columnTitle":"<columnTitle>","columnType":"text"}`

### `mondaymcp_createdashboard`

CreateDashboard · Write

Use this tool to create a new monday.com dashboard that aggregates data from one or more boards. 
    Dashboards provide visual representations of board data through widgets and charts.

    Use this tool when users want to:
    - Create a dashboard to visualize board data
    - Aggregate information from multiple boards
    - Set up a data visualization container for widgets

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `board_ids` (`array`, required): List of board IDs as strings (min 1 element)
- `name` (`string`, required): Human-readable dashboard title (UTF-8 chars)
- `workspace_id` (`string`, required): ID of the workspace that will own the dashboard
- `board_folder_id` (`string`, optional): Optional folder ID within workspace to place this dashboard (if not provided, dashboard will be placed in workspace root)
- `kind` (`string`, optional): Visibility level: PUBLIC or PRIVATE. One of: `PRIVATE`, `PUBLIC`. Default: `PUBLIC`.

Example input: `{"board_ids":[],"name":"High Priority Items","workspace_id":"<workspace_id>"}`

### `mondaymcp_createdoc`

CreateDoc · Write

Create a new monday.com doc either inside a workspace or attached to an item (via a doc column). After creation, the provided markdown will be appended to the document.

LOCATION TYPES:
- workspace: Creates a document in a workspace (requires workspace_id, optional doc_kind, optional folder_id, optional docOwnerIds)
- item: Creates a document attached to an item (requires item_id, optional column_id, optional docOwnerIds)

USAGE EXAMPLES:
- Workspace doc: { location: "workspace", workspace_id: 123, doc_name: "My Doc", doc_kind: "private" , markdown: "..." }
- Workspace doc in folder: { location: "workspace", workspace_id: 123, doc_name: "My Doc", folder_id: 17264196 , markdown: "..." }
- Item doc: { location: "item", item_id: 456, doc_name: "My Doc", column_id: "doc_col_1" , markdown: "..." }
- Workspace doc with agent owner: { location: "workspace", workspace_id: 123, doc_name: "My Doc", markdown: "...", docOwnerIds: ["<agent_owner_user_id>"] }

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `doc_name` (`string`, required): Name for the new document.
- `location` (`string`, required): Location where the document should be created - either in a workspace or attached to an item. One of: `workspace`, `item`.
- `markdown` (`string`, required): Markdown content that will be imported into the newly created document as blocks.
- `column_id` (`string`, optional): [OPTIONAL - use only when location="item"] ID of an existing "doc" column on the board which contains the item. If not provided, the tool will create a new doc column automatically when creating a doc on an item.
- `doc_kind` (`string`, optional): [OPTIONAL - use only when location="workspace"] Document kind (public/private/share). Defaults to public. One of: `private`, `public`, `share`.
- `docOwnerIds` (`array`, optional): Optional list of user IDs to set as document owners at creation time. Use this to add the agent owner so they retain access to the document. Ownership is set inside the creation mutation itself, bypassing the permission checks that would block a subsequent add_subscribers_to_object call.
- `folder_id` (`number`, optional): [OPTIONAL - use only when location="workspace"] Optional folder ID to place the document inside a specific folder
- `item_id` (`number`, optional): [REQUIRED - use only when location="item"] Item ID to attach the new document to
- `workspace_id` (`number`, optional): [REQUIRED - use only when location="workspace"] Workspace ID under which to create the new document

Example input: `{"doc_name":"<doc_name>","location":"workspace","markdown":"<markdown>"}`

### `mondaymcp_createfolder`

CreateFolder · Write

Create a new folder in a monday.com workspace

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the folder to be created
- `workspaceId` (`string`, required): The ID of the workspace where the folder will be created
- `color` (`string`, optional): The color of the folder. One of: `AQUAMARINE`, `BRIGHT_BLUE`, `BRIGHT_GREEN`, `CHILI_BLUE`, `DARK_ORANGE`, `DARK_PURPLE`, `DARK_RED`, `DONE_GREEN`, `INDIGO`, `LIPSTICK`, `NULL`, `PURPLE`, `SOFIA_PINK`, `STUCK_RED`, `SUNSET`, `WORKING_ORANGE`.
- `customIcon` (`string`, optional): The custom icon of the folder. One of: `FOLDER`, `MOREBELOW`, `MOREBELOWFILLED`, `NULL`, `WORK`.
- `fontWeight` (`string`, optional): The font weight of the folder. One of: `FONT_WEIGHT_BOLD`, `FONT_WEIGHT_LIGHT`, `FONT_WEIGHT_NORMAL`, `FONT_WEIGHT_VERY_LIGHT`, `NULL`.
- `parentFolderId` (`string`, optional): The ID of the parent folder

Example input: `{"name":"High Priority Items","workspaceId":"<workspaceId>"}`

### `mondaymcp_createform`

CreateForm · Write

Create a monday.com form. Also creates a backing board to store responses. Returns the formToken for future mutations.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `destination_workspace_id` (`string`, required): No description.
- `board_kind` (`string`, optional): No description. One of: `private`, `public`, `share`.
- `board_owner_ids` (`array`, optional): No description.
- `board_owner_team_ids` (`array`, optional): No description.
- `board_subscriber_ids` (`array`, optional): User IDs to notify on board activity.
- `board_subscriber_teams_ids` (`array`, optional): Team IDs to notify on board activity.
- `destination_folder_id` (`string`, optional): No description.
- `destination_folder_name` (`string`, optional): No description.
- `destination_name` (`string`, optional): Board name (stores form responses).

Example input: `{"destination_workspace_id":"<destination_workspace_id>"}`

### `mondaymcp_createformsubmission`

CreateFormSubmission · Write

Submit a response to a monday.com WorkForm. Use get_form first to retrieve the WorkForm, then:
- Inspect each question's showIfRules to determine which questions are conditionally shown based on previous answers.
- Inspect each question's settings for any answer constraints (e.g. rating limits, select options, label limits).
- Take note of any titles, descriptions, and content blocks to present the form naturally as you walk the user through it.
- Take note of pages and question order to present questions in the correct sequence.
Gather all answers upfront before calling this tool — do not submit one question at a time. Accepts a bare form token, a full WorkForm URL (e.g. https://forms.monday.com/forms/{form_token}?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t) — shortened URLs are automatically resolved by following the redirect. Returns the submission ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `answers` (`array`, required): Array of answers to submit. Each answer specifies a question_id and the value for that question type.
- `form_timezone_offset` (`integer`, required): The timezone offset of the submitter in minutes (e.g. -120 for UTC-2, 0 for UTC).
- `form_token` (`string`, required): The unique token identifying the WorkForm. Can be a bare token, a full WorkForm URL (e.g. https://forms.monday.com/forms/abc123?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t). Shortened URLs are automatically resolved by following the redirect.
- `password` (`string`, optional): The password for the WorkForm. Only required if the WorkForm has password protection enabled (check features.password.enabled from get_form). If required, ask the user for the password before submitting.
- `tags` (`array`, optional): Tags to attach to the submission — each tag maps a value to a specific board column.

Example input: `{"answers":[],"form_timezone_offset":-120,"form_token":"<form_token>"}`

### `mondaymcp_creategroup`

CreateGroup · Write

Create a new group in a monday.com board. Groups are sections that organize related items. Use when users want to add structure, categorize items, or create workflow phases. Groups can be positioned relative to existing groups and assigned predefined colors. Items will always be created in the top group and so the top group should be the most relevant one for new item creation

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The ID of the board to create the group in
- `groupName` (`string`, required): The name of the new group (maximum 255 characters)
- `groupColor` (`string`, optional): The color for the group. Must be one of the predefined Monday.com group colors: #037f4c, #00c875, #9cd326, #cab641, #ffcb00, #784bd1, #9d50dd, #007eb5, #579bfc, #66ccff, #bb3354, #df2f4a, #ff007f, #ff5ac4, #ff642e, #fdab3d, #7f5347, #c4c4c4, #757575. One of: `#037f4c`, `#00c875`, `#9cd326`, `#cab641`, `#ffcb00`, `#784bd1`, `#9d50dd`, `#007eb5`, `#579bfc`, `#66ccff`, `#bb3354`, `#df2f4a`, `#ff007f`, `#ff5ac4`, `#ff642e`, `#fdab3d`, `#7f5347`, `#c4c4c4`, `#757575`.
- `positionRelativeMethod` (`string`, optional): Whether to position the new group before or after the relativeTo group. One of: `after_at`, `before_at`.
- `relativeTo` (`string`, optional): The ID of the group to position this new group relative to

Example input: `{"boardId":"<boardId>","groupName":"<groupName>"}`

### `mondaymcp_createitem`

CreateItem · Write

Create a new item with provided values, create a subitem under a parent item, or duplicate an existing item and update it with new values. Use parentItemId when creating a subitem under an existing item. Use duplicateFromItemId when copying an existing item with modifications.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper column values and knowing which columns are available.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`number`, required): The id of the board to which the new item will be added
- `columnValues` (`string`, required): A string containing the new column values for the item following this structure: {\"column_id\": \"value\",... you can change multiple columns at once, note that for status column you must use nested value with 'label' as a key and for date column use 'date' as key} - example: "{\"text_column_id\":\"New text\", \"status_column_id\":{\"label\":\"Done\"}, \"date_column_id\":{\"date\":\"2023-05-25\"},\"dropdown_id\":\"value\", \"phone_id\":\"123-456-7890\", \"email_id\":\"test@example.com\"}"
- `name` (`string`, required): The name of the new item to be created, must be relevant to the user's request
- `createLabelsIfMissing` (`boolean`, optional): When true, missing status/dropdown labels referenced in columnValues will be auto-created on the board instead of erroring with ColumnValueException. Requires permission to change board structure. Use when the caller specifies label names that may not yet exist on the board.
- `duplicateFromItemId` (`number`, optional): The id of existing item to duplicate and update with new values (only provide when duplicating)
- `groupId` (`string`, optional): The id of the group id to which the new item will be added, if its not clearly specified, leave empty
- `parentItemId` (`number`, optional): The id of the parent item under which the new subitem will be created

Example input: `{"boardId":1,"columnValues":"<columnValues>","name":"High Priority Items"}`

### `mondaymcp_createitems`

Create Multiple Items · Write

Create up to 20 new items in a single call. Each item is fully independent - it chooses its own groupId, parentItemId (for subitems), duplicateFromItemId (for bulk templating from an existing item), and createLabelsIfMissing. A single call can therefore span multiple groups, mix regular items with subitems under different parents, and mix fresh creates with duplicates of existing items. Each item returns its own item_id and item_url on success, or a raw error message on failure. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use get_board_info to understand the board metadata. This is essential for constructing proper column values and knowing which columns are available.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`number`, required): The id of the board to which the new items will be added
- `items` (`array`, required): The items to create, up to 20 per call. Each item returns its own item_id and item_url on success, or a raw error message on failure. Each item independently chooses its groupId, parentItemId, and createLabelsIfMissing.

Example input: `{"boardId":1,"items":[]}`

### `mondaymcp_createnotification`

CreateNotification · Write

Send a notification to a user via the bell icon and optionally by email. Use target_type "Post" for updates/replies or "Project" for items/boards.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `target_id` (`string`, required): The target ID (update/reply ID for Post type, item/board ID for Project type)
- `target_type` (`string`, required): The target type (Post for update/reply, Project for item/board). One of: `Post`, `Project`.
- `text` (`string`, required): The notification text
- `user_id` (`string`, required): The user ID to send the notification to

Example input: `{"target_id":"<target_id>","target_type":"Post","text":"<text>","user_id":"<user_id>"}`

### `mondaymcp_createupdate`

CreateUpdate · Write

Create a new update (comment/post) on a monday.com item. Updates can be used to add comments, notes, or discussions to items. You can optionally mention users, teams, or boards in the update. You can also reply to an existing update by using the parentId parameter.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): The update text to be created. Do not use @ to mention users, use the mentionsList field instead. use html tags to format the text, dont use markdown.
- `itemId` (`number`, required): The id of the item to which the update will be added
- `mentionsList` (`string`, optional): Optional JSON array of mentions in the format: [{"id": "123", "type": "User"}, {"id": "456", "type": "Team"}]. Valid types are: User, Team, Board, Project
- `parentId` (`number`, optional): The ID of the update to reply to. Use this parameter when you want to reply on an existing update leave it empty if you want to create a new update

Example input: `{"body":"<body>","itemId":1}`

### `mondaymcp_createview`

CreateView · Write

Create a new board view (tab) with optional filters and sorting. This creates a saved view on a monday.com board that users can switch to.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] }
Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The board ID to create the view on
- `filter` (`object`, optional): Filter configuration for the view
- `name` (`string`, optional): The name of the view (e.g. "High Priority Items", "My Tasks")
- `settings` (`string`, optional): Type-specific view settings as a JSON object (e.g. column visibility, group_by for TABLE). The shape varies by view type — call get_view_schema_by_type with the same ViewKind to discover the supported structure. For TABLE views, prefer the dedicated create_view_table tool which exposes a strongly-typed settings field.
- `sort` (`array`, optional): Sort configuration for the view
- `type` (`string`, optional): The type of board view to create. Use TABLE for standard board views. One of: `APP`, `DASHBOARD`, `FORM`, `TABLE`. Default: `TABLE`.

Example input: `{"boardId":"<boardId>"}`

### `mondaymcp_createviewtable`

CreateViewTable · Write

Create a new table-type board view with optional filters, sort, tags, and table-specific settings (column visibility/order and group-by). Use this instead of create_view when you need to configure table-specific settings. For a simple table view, create_view also works.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] }
Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The board ID to create the table view on
- `filter` (`object`, optional): Filter configuration for the view
- `name` (`string`, optional): The name of the view (e.g. "High Priority Items", "My Tasks")
- `settings` (`object`, optional): Table-specific view settings (column visibility/order, group-by)
- `sort` (`array`, optional): Sort configuration for the view
- `tags` (`array`, optional): Tags to apply to the view

Example input: `{"boardId":"<boardId>"}`

### `mondaymcp_createwidget`

CreateWidget · Write

Create a new widget in a dashboard or board view with specific configuration settings.

    This tool creates data visualization widgets that display information from monday.com boards:
    **Parent Containers:**
    - **DASHBOARD**: Place widget in a dashboard (most common use case)
    - **BOARD_VIEW**: Place widget in a specific board view

    **Critical Requirements:**
    1. **Schema Compliance**: Widget settings MUST conform to the JSON schema for the specific widget type
    2. **Use all_widgets_schema first**: Always fetch widget schemas before creating widgets
    3. **Validate settings**: Ensure all required fields are provided and data types match

    **Workflow:**
    1. Use 'all_widgets_schema' to get schema definitions
    2. Prepare widget settings according to the schema
    3. Use this tool to create the widget

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `parent_container_id` (`string`, required): ID of the parent container (dashboard ID or board view ID)
- `parent_container_type` (`string`, required): Type of parent container: DASHBOARD or BOARD_VIEW. One of: `BOARD_VIEW`, `DASHBOARD`.
- `widget_kind` (`string`, required): Type of widget to create: i.e CHART, NUMBER, BATTERY. One of: `APP_FEATURE`, `BATTERY`, `CALENDAR`, `CHART`, `GANTT`, `LISTVIEW`, `NUMBER`.
- `widget_name` (`string`, required): Widget display name (1-255 UTF-8 chars)
- `settings` (`object`, optional): Widget-specific settings as JSON object conforming to widget schema. Use all_widgets_schema tool to get the required schema for each widget type.

Example input: `{"parent_container_id":"<parent_container_id>","parent_container_type":"BOARD_VIEW","widget_kind":"APP_FEATURE","widget_name":"<widget_name>"}`

### `mondaymcp_createworkflow`

CreateWorkflow · Write

Creates a new empty workflow in a monday.com workspace.

Use this when the user wants to build a new standalone workflow from scratch. Workflows are cross-board, workspace-level — distinct from automations (use create_automation for those). You only need a workspaceId to get started — all other fields are optional.

Returns:
- workflowObjectId: the workflow object ID
- workflowDraftId: the current draft version ID — workflows start as drafts and must be published before they run

Terminology:
- Workflows vs. automations: workflows are standalone objects scoped to a workspace. Automations (create_automation) are per-board trigger/action rules. They are different products.
- Draft: the editable, inactive version of a workflow. Changes are made on the draft version until it is published as the live version.
- Privacy: PUBLIC — visible to all workspace members (default). PRIVATE — restricted access. SHAREABLE — accessible to guests outside the account.

Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `workspaceId` (`string`, required): The ID of the workspace to create the workflow in.
- `description` (`string`, optional): Optional workflow description.
- `folderId` (`string`, optional): Optional folder ID to place the workflow in.
- `ownerIds` (`array`, optional): Optional list of user IDs to set as workflow owners.
- `privacyKind` (`string`, optional): Privacy kind for the workflow (defaults to PUBLIC). One of: `PUBLIC`, `PRIVATE`, `SHARE`.
- `title` (`string`, optional): Workflow title. Defaults to "New Workflow" if not provided.

Example input: `{"workspaceId":"<workspaceId>"}`

### `mondaymcp_createworkspace`

CreateWorkspace · Write

Create a new workspace in monday.com

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the new workspace to be created
- `workspaceKind` (`string`, required): The kind of workspace to create. One of: `closed`, `open`, `template`.
- `accountProductId` (`string`, optional): The account product ID associated with the workspace
- `description` (`string`, optional): The description of the new workspace

Example input: `{"name":"High Priority Items","workspaceKind":"closed"}`

### `mondaymcp_finalizeassetupload`

FinalizeAssetUpload · Write

Finalize a file upload and create the asset on monday.com. Call this after uploading the file to the presigned URL from get_asset_upload_url. Requires the etag value from the PUT response headers. Automatically attaches the uploaded asset to the specified file column on the item. Returns the created asset_id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`string`, required): The board's unique identifier
- `columnId` (`string`, required): The file or doc column's unique identifier to attach the uploaded asset to
- `etag` (`string`, required): The ETag header value from the PUT response when uploading to the presigned URL
- `itemId` (`string`, required): The item's unique identifier
- `uploadId` (`string`, required): The upload_id returned by get_asset_upload_url

Example input: `{"boardId":"<boardId>","columnId":"<columnId>","etag":"<etag>","itemId":"<itemId>","uploadId":"<uploadId>"}`

### `mondaymcp_getassetuploadurl`

GetAssetUploadUrl · Write

Get a presigned URL to upload a file to monday.com. Returns an upload_id and upload_url.

After calling this tool, upload the file to the returned URL using an HTTP PUT request and capture the ETag header from the response:

curl -i -X PUT "<upload_url>" \
  -H "Content-Type: <the contentType you provided>" \
  --data-binary @<local_file_path>

The response includes an ETag header (e.g. ETag: "abc123...") — save this value.

Then call finalize_asset_upload with the upload_id, etag, board_id, item_id, and column_id to complete the upload and attach the file to an item's file column.

Max file size: 500MB.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `contentType` (`string`, required): The MIME type of the file (e.g. "application/pdf", "image/png", "text/plain")
- `fileName` (`string`, required): The name of the file to upload, including extension (e.g. "report.pdf")
- `fileSize` (`integer`, required): The file size in bytes. Maximum 500MB (524288000 bytes)

Example input: `{"contentType":"application/pdf","fileName":"report.pdf","fileSize":1}`

### `mondaymcp_manageagentknowledge`

ManageAgentKnowledge · Write

List, grant, update, or revoke a monday platform agent's access to boards and docs.

An agent's "knowledge" is the set of monday.com boards and docs it can read from or write to during a run.

- list: Returns all resources the agent currently has access to, including permission level and resource type.
- add: Grants the agent access to a board or doc with the specified permission level.
- update: Changes the permission level on a resource the agent already has access to. Call action:"list" first to confirm the resource_id exists.
- remove: Revokes the agent's access to a board or doc entirely. Call action:"list" first to confirm the resource_id exists.

Permission types:
- READ: Agent can read data from the resource.
- READ_WRITE: Agent can read and write data to the resource.

USAGE EXAMPLES:
- List: { "action": "list", "agent_id": "7" }
- Add board access: { "action": "add", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ" }
- Update to read-write: { "action": "update", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD", "permission_type": "READ_WRITE" }
- Remove access: { "action": "remove", "agent_id": "7", "resource_id": "42", "scope_type": "BOARD" }

RELATED TOOLS:
- manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)
- manage_agent_triggers — manage which triggers fire this agent automatically
- manage_agent_skills — manage which skills this agent can perform

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): "list" — returns all resources the agent currently has access to. "add" — grants access to a board or doc. "update" — changes the permission level on an existing resource. "remove" — revokes the agent's access to a board or doc. One of: `list`, `add`, `update`, `remove`.
- `agent_id` (`string`, required): Unique identifier of the agent.
- `permission_type` (`string`, optional): Required for action:add and action:update. The permission level: "READ" (agent can read the resource) or "READ_WRITE" (agent can read and write the resource). One of: `READ`, `READ_WRITE`.
- `resource_id` (`string`, optional): Required for action:add, action:update, action:remove. The ID of the board or doc to grant/update/revoke access to.
- `scope_type` (`string`, optional): Required for action:add, action:update, action:remove. The type of resource: "BOARD" or "DOC". One of: `BOARD`, `DOC`.

Example input: `{"action":"list","agent_id":"<agent_id>"}`

### `mondaymcp_manageagentskills`

ManageAgentSkills · Write

Manage the full skill lifecycle for monday platform agents — create new skills in the catalog, attach skills to an agent, or detach them.

Skills extend what an agent can do (e.g. sending emails, querying databases, posting to Slack).

ACTIONS:
- create: { name, content, description? } — creates a new custom skill in the account-wide catalog.
  The skill becomes available to all agents in the account.
- add:    { agent_id, skill_id } — attaches a skill to this agent.
- remove: { agent_id, skill_id } — detaches a skill from this agent.

WORKFLOW — attach an existing skill:
1. Call agent_catalog action:"list_skills" — find the skill_id of the skill to attach.
2. Call this tool action:"add" with agent_id and that skill_id.

WORKFLOW — create a new skill and attach it:
1. Call this tool action:"create" with name and content — note the returned id.
2. Call this tool action:"add" with agent_id and that id directly (no catalog lookup needed).

NOTE: There is no action to list which skills are currently attached to a specific agent — the platform does not yet expose that query.
To browse all skills available in the account catalog, use agent_catalog action:"list_skills".

USAGE EXAMPLES:
- Create a skill:  { "action": "create", "name": "Send Slack Message", "content": "## Instructions\nPost a message to a Slack channel.", "description": "Sends a message to Slack" }
- Add a skill:     { "action": "add", "agent_id": "7", "skill_id": "skill-abc-123" }
- Remove a skill:  { "action": "remove", "agent_id": "7", "skill_id": "skill-abc-123" }

RELATED TOOLS:
- agent_catalog action:"list_skills" — browse existing skills to find a skill_id before calling action:"add"
- manage_agent_triggers — manage which triggers fire this agent automatically
- manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): "create" — author a new custom skill in the account-wide catalog (no agent_id needed). "add" — attach an existing skill to this agent by skill_id. "remove" — detach a skill from this agent. One of: `create`, `add`, `remove`.
- `agent_id` (`string`, optional): Required for action:"add" and action:"remove". Not used for action:"create" (account-level operation).
- `content` (`string`, optional): Required for action:"create". Markdown instructions defining what the skill does and how to execute it. Be specific and thorough — this is the skill's runtime behavior.
- `description` (`string`, optional): Used with action:"create". Short description shown in the catalog.
- `name` (`string`, optional): Required for action:"create". Display name of the new skill.
- `skill_id` (`string`, optional): Required for action:"add" and action:"remove". The skill id from agent_catalog action:"list_skills", or the id returned by action:"create" in this tool. Never guess or invent a skill id.

Example input: `{"action":"create"}`

### `mondaymcp_manageagenttriggers`

ManageAgentTriggers · Write

Manage the triggers attached to a monday platform agent — triggers define WHEN the agent runs automatically.

ACTIONS:
- list:   { agent_id } — returns active triggers with node_id, block_reference_id, name, field_summary.
- add:    { agent_id, block_reference_id, field_values? } — attaches a trigger type to the agent.
- remove: { agent_id, node_id } — detaches a trigger instance by node_id (NOT block_reference_id).

WORKFLOW — add a trigger:
1. Call agent_catalog action:"list_triggers" — note block_reference_id, field_schemas, and required_fields.
2. Collect required field values from the user (e.g. board_id, column_id).
3. Call this tool action:"add" with block_reference_id and field_values.
Note: add returns only { success } — no node_id for the new instance. Call action:"list" afterward if you need the node_id.

WORKFLOW — remove a trigger:
1. Call action:"list" to see active triggers and note the node_id of the instance to remove.
2. Call action:"remove" with that node_id.

NOTE: Only triggers that can be added programmatically appear in the catalog. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.)
require user setup in the monday.com UI — they will not appear in agent_catalog and cannot be managed here.

USAGE EXAMPLES:
- List triggers:  { "action": "list", "agent_id": "7" }
- Add trigger:    { "action": "add", "agent_id": "7", "block_reference_id": "status-change-ref", "field_values": { "board_id": "42" } }
- Remove trigger: { "action": "remove", "agent_id": "7", "node_id": "node-abc" }

RELATED TOOLS:
- agent_catalog action:"list_triggers" — discover available trigger types and their required field_values before calling action:"add" here
- manage_agent_skills — manage which skills this agent can perform
- manage_agent — manage the agent entity itself (create, activate, deactivate, etc.)

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): "list" — returns all triggers currently attached to this agent (includes node_id needed for remove). "add" — attaches a new trigger by block_reference_id. "remove" — detaches a trigger instance by node_id. One of: `list`, `add`, `remove`.
- `agent_id` (`string`, required): Unique identifier of the agent.
- `block_reference_id` (`string`, optional): Required for action:"add". The block_reference_id from agent_catalog action:"list_triggers" identifying the trigger type to attach. Never guess this value — look it up in the catalog first.
- `field_values` (`object`, optional): Used with action:"add" when the trigger type has required_fields. Key/value object whose shape is described by field_schemas in the agent_catalog response. Scalar fields use string/number/boolean values. Selection fields use { "value": "<id>", "label": "<name>" }.
- `node_id` (`string`, optional): Required for action:"remove". The node_id of the trigger instance — get it from action:"list". Each instance has a unique node_id even if the same trigger type is attached multiple times. Do NOT pass block_reference_id here.

Example input: `{"action":"list","agent_id":"<agent_id>"}`

### `mondaymcp_moveobject`

MoveObject · Write

Move a folder, board, or overview in monday.com. Use position for relative placement based on another object, parentFolderId for folder changes, workspaceId for workspace moves, and accountProductId for account product changes.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the object to move
- `objectType` (`string`, required): The type of object to move. One of: `Board`, `Folder`, `Overview`.
- `accountProductId` (`string`, optional): The ID of the account product containing the object. Required if moving to a different account product.
- `parentFolderId` (`string`, optional): The ID of the new parent folder. Required if moving to a different folder.
- `position_is_after` (`boolean`, optional): Whether to position the object after the object
- `position_object_id` (`string`, optional): The ID of the object to position the object relative to. If this parameter is provided, position_object_type must be also provided.
- `position_object_type` (`string`, optional): The type of object to position the object relative to. If this parameter is provided, position_object_id must be also provided. One of: `Board`, `Folder`, `Overview`.
- `workspaceId` (`string`, optional): The ID of the workspace containing the object. Required if moving to a different workspace.

Example input: `{"id":"<id>","objectType":"Board"}`

### `mondaymcp_publishworkflow`

PublishWorkflow · Write

Publishes a workflow draft, promoting it to the live version.

Use this after create_workflow (and optionally update_workflow) to make the workflow active. Before publishing, the workflow is validated — if it has missing or misconfigured steps, publish will fail with a WORKFLOW_VALIDATION_FAILED error that includes structured issue details: which step failed, the issue type, and which inputs are missing. Use those details to guide the user on what to fix before retrying.

Parameters:
- workflowObjectId and workflowDraftId: returned by create_workflow — they identify which draft to publish.
- shouldActivate: whether to activate the workflow immediately after publish. Defaults to true — pass false to publish without activating.

Returns:
- workflowObjectId: the workflow object ID (unchanged)
- workflowLiveId: the new live version ID — this changes on every publish, so do not cache it

Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `workflowDraftId` (`number`, required): The identifier of a draft that belongs to the workflow object referenced by workflowObjectId.
- `workflowObjectId` (`number`, required): The identifier of a workflow object, found in the workflow URL. A workflow object is the entity that is retained across published versions; users can create draft versions related to this workflow object.
- `shouldActivate` (`boolean`, optional): Whether to activate the workflow immediately after publishing so it starts running. Defaults to true — the workflow is activated immediately after publish.

Example input: `{"workflowDraftId":1,"workflowObjectId":1}`

### `mondaymcp_updatecolumn`

Update Column · Write

Update properties of an existing monday.com column (title, description, settings). Uses optimistic concurrency control via the revision field — fetch the current revision via get_board_schema first, then call this tool. If the update fails because the revision is stale, re-fetch and try again.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `boardId` (`number`, required): The id of the board containing the column
- `columnId` (`string`, required): The id of the column to update
- `columnType` (`string`, required): The type of the column being updated. Must match the existing column type. One of: `auto_number`, `board_relation`, `button`, `checkbox`, `color_picker`, `country`, `creation_log`, `date`, `dependency`, `direct_doc`, `doc`, `dropdown`, `email`, `file`, `formula`, `group`, `hour`, `integration`, `item_assignees`, `item_id`, `last_updated`, `link`, `location`, `long_text`, `mirror`, `name`, `numbers`, `people`, `phone`, `progress`, `rating`, `status`, `subtasks`, `tags`, `team`, `text`, `time_tracking`, `timeline`, `unsupported`, `vote`, `week`, `world_clock`.
- `revision` (`string`, required): The current revision of the column, obtained from get_board_schema. Used for optimistic concurrency control: if the column changed since you read it, the request will fail and you should re-fetch the latest revision before retrying.
- `columnDescription` (`string`, optional): The new description of the column. If omitted, the description is unchanged.
- `columnSettings` (`string`, optional): Type-specific configuration as a JSON string. Use get_column_type_info with fetchMode "schema" for the JSON schema for the given column type. If omitted, settings are unchanged.
- `columnTitle` (`string`, optional): The new title of the column. If omitted, the title is unchanged.

Example input: `{"boardId":1,"columnId":"<columnId>","columnType":"text","revision":"<revision>"}`

### `mondaymcp_updatefolder`

UpdateFolder · Write

Update an existing folder in monday.com

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `folderId` (`string`, required): The ID of the folder to update
- `accountProductId` (`string`, optional): The account product ID associated with the folder
- `color` (`string`, optional): The new color of the folder. One of: `AQUAMARINE`, `BRIGHT_BLUE`, `BRIGHT_GREEN`, `CHILI_BLUE`, `DARK_ORANGE`, `DARK_PURPLE`, `DARK_RED`, `DONE_GREEN`, `INDIGO`, `LIPSTICK`, `NULL`, `PURPLE`, `SOFIA_PINK`, `STUCK_RED`, `SUNSET`, `WORKING_ORANGE`.
- `customIcon` (`string`, optional): The new custom icon of the folder. One of: `FOLDER`, `MOREBELOW`, `MOREBELOWFILLED`, `NULL`, `WORK`.
- `fontWeight` (`string`, optional): The new font weight of the folder. One of: `FONT_WEIGHT_BOLD`, `FONT_WEIGHT_LIGHT`, `FONT_WEIGHT_NORMAL`, `FONT_WEIGHT_VERY_LIGHT`, `NULL`.
- `name` (`string`, optional): The new name of the folder
- `parentFolderId` (`string`, optional): The ID of the new parent folder
- `position_is_after` (`boolean`, optional): Whether to position the folder after the object
- `position_object_id` (`string`, optional): The ID of the object to position the folder relative to. If this parameter is provided, position_object_type must be also provided.
- `position_object_type` (`string`, optional): The type of object to position the folder relative to. If this parameter is provided, position_object_id must be also provided. One of: `Board`, `Folder`, `Overview`.
- `workspaceId` (`string`, optional): The ID of the workspace containing the folder

Example input: `{"folderId":"<folderId>"}`

### `mondaymcp_updateform`

UpdateForm · Write

Update a monday.com form. Use the action field to specify the operation.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `action` (`string`, required): Action to execute on the form. Each action requires different fields — check field descriptions to know what to include. One of: `activate`, `deactivate`, `shortenFormUrl`, `setFormPassword`, `createTag`, `deleteTag`, `updateAppearance`, `updateAccessibility`, `updateFeatures`, `updateQuestionOrder`, `updateFormHeader`.
- `formToken` (`string`, required): No description.
- `form` (`object`, optional): Form data to update (patch semantics).
- `formPassword` (`string`, optional): Required for setFormPassword action.
- `tag` (`object`, optional): Tag to create/delete. Delete: id only. Create: name (id/columnId auto-generated).

Example input: `{"action":"activate","formToken":"<formToken>"}`

### `mondaymcp_updateitems`

Update Multiple Items · Write

Update column values for up to 40 items in a single call. Each update targets one item by itemId and sets one or more column values on it. Each update is independent - it can target its own board via boardId and set its own column values, so a single call can update many items across multiple boards, apply the same value to many items, or apply different values per item. Each update returns its own item_id and item_url on success or a raw error message on failure. To link board-relation columns, call link_board_items_workflow before using this tool. [REQUIRED PRECONDITION]: Before using this tool, if you are not familiar with the board structure (column IDs, column types, status labels), first use get_board_info to understand the board metadata. This is essential for constructing valid column values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `updates` (`array`, required): The item updates to apply, up to 40 per call. Each entry updates one item and returns its own result on success or a raw error message on failure. Each entry independently chooses its boardId, columnValues, and createLabelsIfMissing.
- `boardId` (`number`, optional): Optional default board id used for any update that does not set its own boardId. Each update can override it with its own boardId, so a single call can span multiple boards.

Example input: `{"updates":[]}`

### `mondaymcp_updateview`

UpdateView · Write

Update an existing board view (tab) — change its name, filter rules, or sort order. Provide only the fields you want to change. Omitted fields are left unchanged.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example filter for people column: { "rules": [{ "column_id": "people", "compare_value": ["person-12345"], "operator": "any_of" }] }
Example filter for status column: { "rules": [{ "column_id": "status", "compare_value": [1], "operator": "any_of" }] }

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`string`, required): The board ID the view belongs to
- `viewId` (`string`, required): The ID of the view to update
- `filter` (`object`, optional): Filter configuration to apply to the view
- `name` (`string`, optional): New name for the view (omit to leave unchanged)
- `settings` (`string`, optional): Type-specific view settings as a JSON object (e.g. column visibility, group_by for TABLE). The shape varies by view type — call get_view_schema_by_type with the same ViewKind to discover the supported structure. For TABLE views, prefer the dedicated update_view_table tool which exposes a strongly-typed settings field.
- `sort` (`array`, optional): Sort configuration for the view
- `type` (`string`, optional): The type of the board view being updated. Use TABLE for standard board views. One of: `APP`, `DASHBOARD`, `FORM`, `TABLE`. Default: `TABLE`.

Example input: `{"boardId":"<boardId>","viewId":"<viewId>"}`

### `mondaymcp_updateviewtable`

UpdateViewTable · Write

Update an existing table-type board view — change its name, filters, sort, tags, or table-specific settings (column visibility/order and group-by). Provide only the fields you want to change. Omitted fields are left unchanged.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] }
Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `boardId` (`string`, required): The board ID the view belongs to
- `viewId` (`string`, required): The ID of the table view to update
- `filter` (`object`, optional): Filter configuration to apply to the view
- `name` (`string`, optional): New name for the view (omit to leave unchanged)
- `settings` (`object`, optional): Table-specific view settings (column visibility/order, group-by)
- `sort` (`array`, optional): Sort configuration for the view
- `tags` (`array`, optional): Tags to apply to the view

Example input: `{"boardId":"<boardId>","viewId":"<viewId>"}`

### `mondaymcp_updateworkflow`

UpdateWorkflow · Write

Updates an existing workflow draft using an AI agent.

The agent interprets the prompt and applies structural changes to the workflow — creating, updating, or deleting steps. Pass clear, descriptive instructions and the agent will decide which operations to perform, then return a summary of what it did.

Use this after create_workflow to build out the workflow step by step. You can call it multiple times on the same draft to iteratively refine the workflow.

Parameters:
- workflowObjectId and workflowDraftId: both returned by create_workflow — they identify which draft to update.
- prompt: describe what you want to change in plain English (e.g. "Add a trigger that fires when an item is created on the Marketing board"). Maximum 2000 characters.

Returns:
- workflowObjectId: the workflow object ID (unchanged)
- workflowDraftId: the draft version ID (unchanged)
- result: agent response describing the changes made

Note: if directing the user to the workflow in the UI, the correct URL path is custom_objects/, not workflows/ — e.g. {account}.monday.com/custom_objects/{workflowObjectId}.

Note: the workflow runs only after it is published to live version.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `prompt` (`string`, required): Natural-language description of the changes to make. Describe what steps to add, remove, or modify in plain English (e.g. "Add a trigger that fires when an item is created on the Marketing board"). The agent interprets this and applies the right structural changes. Maximum 2000 characters.
- `workflowDraftId` (`number`, required): The draft version ID to update. Use the workflowDraftId from the previous create_workflow or update_workflow response — the agent may return a new draft ID, so always read it from the latest response rather than reusing an earlier value.
- `workflowObjectId` (`number`, required): The workflow object ID returned by create_workflow. Identifies the workflow across all its drafts and published versions. Does not change across publishes.

Example input: `{"prompt":"Add a trigger that fires when an item is created on the Marketing board","workflowDraftId":1,"workflowObjectId":1}`

### `mondaymcp_updateworkspace`

UpdateWorkspace · Write

Update an existing workspace in monday.com

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the workspace to update
- `attributeAccountProductId` (`number`, optional): The target account product's ID to move the workspace to
- `attributeDescription` (`string`, optional): The description of the workspace to update
- `attributeKind` (`string`, optional): The kind of the workspace to update (open / closed / template). One of: `closed`, `open`, `template`.
- `attributeName` (`string`, optional): The name of the workspace to update

Example input: `{"id":"<id>"}`

### `mondaymcp_vibecreate`

VibeCreate · Write

Creates a new Vibe app from a natural-language prompt. Returns immediately with app_id and editor_link — the URL of the Vibe builder/chat page for the new app (https://{accountSlug}.monday.com/vibe/app/{appId}); the user can open it right away to watch generation in progress. Generation itself runs asynchronously — poll vibe_get for status. Optional: board_ids to connect existing boards (omit to auto-create), view_id to host a dashboard widget, and model to pick the LLM.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `prompt` (`string`, required): Natural-language description of the app to build
- `board_ids` (`array`, optional): Existing board IDs to connect (they must exist and you must have edit access). For multi-board variants (object, object_fullstack) these are connected as data sources; the number allowed depends on your account tier. For single-board variants (board_view, vibe_dashboard_widget, item views) provide one board id, used as the host board. Omit to have a new board created automatically.
- `model` (`string`, optional): LLM model for code generation. Omit for automatic selection. Requires model selection enabled for the account. One of: `GEMINI_3_5_FLASH`, `CLAUDE_4_5_SONNET`, `CLAUDE_OPUS_4_6`, `GEMINI_3_7_FLASH`, `CLAUDE_5_SONNET`, `CLAUDE_OPUS_5`.
- `variant` (`string`, optional): App variant. One of: `board_view`, `item_view`, `vibe_item_view`, `object`, `vibe_dashboard_widget`, `object_fullstack`, `monday_campaigns`. Default: `object`.
- `view_id` (`string`, optional): Board view ID that hosts the widget — required for vibe_dashboard_widget (the widget is created on this board view), and must be accompanied by its board_id.

Example input: `{"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager"}`

### `mondaymcp_vibepublication`

VibePublication · Write

Manage the publication state of a Vibe app on the caller account. action=publish requires the app to be deployed and respects the published-apps license limit. action=unpublish removes the app from the account.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): publish = make the app live on the caller account; unpublish = remove it from the account. One of: `publish`, `unpublish`.
- `app_id` (`integer`, required): Internal Vibe app id

Example input: `{"action":"publish","app_id":1}`

### `mondaymcp_vibeupdate`

VibeUpdate · Write

Sends a follow-up message to modify an existing app. Fire-and-forget — returns immediately with user_message_id and editor_link (the Vibe builder/chat URL for this app, https://{accountSlug}.monday.com/vibe/app/{appId}). Returns APP_BUSY (409) if the app is currently generating; poll vibe_get first. Optional model to pick the LLM for this build.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `app_id` (`integer`, required): Internal Vibe app id
- `prompt` (`string`, required): Follow-up message describing what to change in the app
- `model` (`string`, optional): LLM model for code generation. Omit for automatic selection. Requires model selection enabled for the account. One of: `GEMINI_3_5_FLASH`, `CLAUDE_4_5_SONNET`, `CLAUDE_OPUS_4_6`, `GEMINI_3_7_FLASH`, `CLAUDE_5_SONNET`, `CLAUDE_OPUS_5`.

Example input: `{"app_id":1,"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager"}`

### `mondaymcp_allapiwrite`

Run Mutation on the monday.com API · Destructive

Execute GraphQL mutations against the monday.com API to create, update, or delete data. Only mutations are accepted — queries are rejected with an error before the request is sent. Use get_graphql_schema and get_type_details tools first to understand the schema before crafting your mutation.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `query` (`string`, required): Custom GraphQL query/mutation. you need to provide the full query / mutation
- `variables` (`string`, required): JSON string containing the variables for the GraphQL operation

Example input: `{"query":"pricing roadmap","variables":"<variables>"}`

### `mondaymcp_allmondayapi`

AllMondayApi · Destructive

Execute any monday.com API operation by generating GraphQL queries and mutations dynamically. Make sure you ask only for the fields you need and nothing more. When providing the query/mutation - use get_graphql_schema and get_type_details tools first to understand the schema before crafting your query.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `query` (`string`, required): Custom GraphQL query/mutation. you need to provide the full query / mutation
- `variables` (`string`, required): JSON string containing the variables for the GraphQL operation

Example input: `{"query":"pricing roadmap","variables":"<variables>"}`

### `mondaymcp_deleteaction`

Delete Action · Destructive

Delete a saved action.

Example:
  id: "550e8400-e29b-41d4-a716-446655440000"

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Action ID

Example input: `{"id":"<id>"}`

### `mondaymcp_executecode`

Execute Code · Destructive

Run arbitrary code in a monday-authenticated sandbox, without saving.

Prefer dedicated monday tools for individual reads, writes, and GraphQL queries/mutations — they render in the UI and are retried one step at a time. Reach for execute_code when code is genuinely the better tool:
  - Bulk / multi-item work — batch operations, dedup, aggregations, joins across boards (one script beats N tool calls that accumulate context and compound failure)
  - Data transformation — normalizing phones/dates, fuzzy matching, weighted scoring
  - File I/O — parsing uploaded CSV/XLSX to import items, producing downloadable exports
  - Multi-step workflows where each step's output gates the next

The sandbox has authenticated access to the monday.com API. You can make HTTP requests with GraphQL queries and mutations — authentication is handled automatically.

IMPORTANT: Network access is restricted to the following hosts: [api.monday.com, mcp.monday.com/mcp]. Requests to any other host (or a different path on a restricted host) will be blocked. Use this tool to query boards, items, columns, users, updates, and any other monday.com API resource.

THE SANDBOX IS PER-CALL: a new empty container every call, destroyed when the call returns. Nothing written to disk survives, /tmp included. Never write a file in one call to read it in a later one, and don't invent staging paths for earlier tool results — none exist. To carry data forward, print it and pass it into the next call's code, or do the whole job in one call. Splitting a fan-out across calls only works if the later calls don't depend on the earlier ones' files.

FAIL WITH A NON-ZERO EXIT. A run that prints an error and exits 0 is recorded as a success. The monday.com API returns HTTP 200 with an "errors" array, so check the parsed body rather than the status code and raise when it is present. Let exceptions propagate; don't wrap the script in a bare try/except.

TIME LIMIT: 300s. A run that exceeds it is killed, so scope each call to finish well inside the limit instead of fetching everything in one script.

Don't call mcp.monday.com from inside the sandbox to reach monday tools — you already have them, and a tool missing from your tool list won't be found there either.

Example — monday.com GraphQL query, raising on errors (Python). Use this shape for every API call:
  code: "import requests\ndef gql(query):\n    body = requests.post('https://api.monday.com/v2', json={'query': query}).json()\n    if 'errors' in body:\n        raise RuntimeError(body['errors'])\n    return body['data']\nprint(gql('{ users(limit:5) { id name email } }'))"

Example — monday.com GraphQL mutation (Python):
  code: "import requests\nmutation = 'mutation { create_board(board_name: \"New Board\", board_kind: public) { id } }'\nbody = requests.post('https://api.monday.com/v2', json={'query': mutation}).json()\nif 'errors' in body:\n    raise RuntimeError(body['errors'])\nprint(body['data'])"

Example — with vars (accessed via os.environ):
  code: "import os, requests\nuser_id = os.environ['user_id']\nresp = requests.post('https://api.monday.com/v2', json={'query': f'{{ users(ids: [{user_id}]) {{ id name email }} }}'})\nprint(resp.json())"
  vars: {"user_id": 12345}

Example — simple (Python):
  code: "print('hello world')"

Example — with files (input and output):
  code: "import json\ndata = json.load(open('/tmp/data.json'))\njson.dump({'count': len(data)}, open('/tmp/result.json', 'w'))"
  files: [{"path": "/tmp/data.json", "content": "W3siaWQiOiAxfV0="}]
  output_files: ["/tmp/result.json"]

Example — auto-collect outputs (write anything you want returned under /outputs):
  code: "import os, json\nos.makedirs('/outputs', exist_ok=True)\njson.dump({'ok': True}, open('/outputs/result.json', 'w'))"
  return_outputs: true

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `code` (`string`, required): Source code to execute. Max 1 MB. Access vars via os.environ (Python), process.env (JS/TS) or "$VAR" (bash).
- `description` (`string`, required): Required. Short summary of what this code does: the data it accesses (specific boards/items by name or ID, or scope if broad), the processing it performs, and how the result is returned.
- `language` (`string`, required): Programming language — one of: javascript, typescript, python, bash. One of: `javascript`, `typescript`, `python`, `bash`.
- `files` (`array`, optional): Input files to write into the sandbox before execution (max 32 files). Each must have content (base64, small files only) or url (S3 presigned URL). Inline content is capped at 512 KB per file and 1 MB across all files, so pass anything larger by url rather than inline content — urls are fetched by the sandbox directly and don't count toward those limits.
- `output_files` (`array`, optional): Absolute file paths to retrieve from the sandbox after execution. Returned as presigned S3 download URLs.
- `return_outputs` (`boolean`, optional): When true, auto-collect every file the code writes under /outputs (instead of naming each path in output_files) and return them as presigned download URLs. Up to 20 files, 25 MB each, 100 MB total; outputs_truncated is set in the response if a limit is hit.
- `vars` (`object`, optional): Variables injected as environment variables into the sandbox (access via os.environ / process.env)

Example input: `{"code":"<code>","description":"<description>","language":"javascript"}`

### `mondaymcp_formquestionseditor`

FormQuestionsEditor · Destructive

Create, update, or delete a question in a monday.com form

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): Action to perform on the question of a form. create requires question. update requires questionId and question with type always included. delete requires questionId. One of: `delete`, `update`, `create`.
- `formToken` (`string`, required): No description.
- `question` (`object`, optional): The question to create or update. Always include type, then only the fields you want to set or change.
- `questionId` (`string`, optional): Question ID. Required for update/delete.

Example input: `{"action":"delete","formToken":"<formToken>"}`

### `mondaymcp_invokeworkflowexpert`

Workflow Expert · Destructive

Workflow expert for a single workflow. Given a prompt, answers questions about the workflow's structure and configuration, or makes changes to it (create, update, delete steps, and configure step fields).

Delegate any prompt that asks about a workflow or asks to change it. Pass clear, descriptive instructions — the expert will decide the right response or operations.

Field values reference resources (boards, columns, people, channels, projects, ...) from monday or any external app — all handled the same way. Pass each resource through as the user stated it; the expert resolves names to IDs and asks the user when it's ambiguous. Pro-tip: pass along any ID you already have to save a follow-up question — no need to look one up first.

Constraints: works on ONE workflow at a time.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `prompt` (`string`, required): A question about the workflow or a description of the changes to make to it
- `workflowObjectId` (`number`, required): The identifier of a workflow object, found in the workflow URL. A workflow object is the entity that is retained across published versions; users can create draft versions related to this workflow object.
- `workflowDraftId` (`number`, optional): The identifier of a draft that belongs to the workflow object referenced by workflowObjectId. When omitted, it refers to the live version of the workflow.

Example input: `{"prompt":"When a deal is marked Won, create a task in the onboarding board and notify the account manager","workflowObjectId":1}`

### `mondaymcp_manageagent`

ManageAgent · Destructive

Full lifecycle management for monday platform agents — create, read, update, delete, change state, and run.

monday platform agents are user-built work orchestrators on monday.com — each has a profile (name, role, avatar), a goal, and a markdown execution plan. Agents in state ACTIVE can be triggered automatically. They are NOT local LangChain or MCP agents.

ACTIONS (only pass fields that apply to the chosen action):
- create:        { action:"create", prompt, agent_model? } — AI-generated agent. Platform creates profile, goal, and plan from the prompt.
- create_blank:  { action:"create_blank", name?, role?, role_description?, avatar_url?, gender?, background_color?, user_prompt? } — manually defined agent.
- get one:       { action:"get", agent_id }
- list owned:    { action:"get" }
- update:        { action:"update", agent_id, name?, role?, role_description?, plan?, agent_model? }
- delete:        { action:"delete", agent_id }
- activate:      { action:"activate", agent_id }
- deactivate:    { action:"deactivate", agent_id }
- run:           { action:"run", agent_id }

RULES:
- "create_blank" with no fields creates a nameless blank agent — only do this intentionally.
- "update" requires at least one of name/role/role_description/plan/agent_model.
- "update", "delete", "activate", "deactivate", "run" all require "agent_id".
- Created agents start INACTIVE. Follow with action:"activate" using the returned agent_id before they can be triggered.
- ⚠️ DESTRUCTIVE — "delete" is permanent and irreversible. When the user refers to an agent by name, ALWAYS call action:"get" first to confirm the correct agent_id before deleting.
- "run" is fire-and-forget. Returns trigger_uuid — no run-status query exists, treat successful enqueue as the only signal.
- Agent state is one of ACTIVE, INACTIVE, ARCHIVED, or FAILED. DELETED only appears as the return value of action:"delete".

USAGE EXAMPLES:
- AI create:    { "action": "create", "prompt": "Run my daily standup every weekday at 9am." }
- Manual create:{ "action": "create_blank", "name": "Standup Bot", "role": "Project Manager", "gender": "female" }
- Fetch one:    { "action": "get", "agent_id": "42" }
- List mine:    { "action": "get" }
- Rename:       { "action": "update", "agent_id": "7", "name": "New Name" }
- Activate:     { "action": "activate", "agent_id": "7" }
- Deactivate:   { "action": "deactivate", "agent_id": "7" }
- Run:          { "action": "run", "agent_id": "7" }
- Delete:       { "action": "delete", "agent_id": "7" }

RELATED TOOLS:
- agent_catalog — browse available trigger types and skills before wiring them to an agent
- manage_agent_triggers — manage which triggers fire this agent automatically
- manage_agent_skills — manage which skills this agent can perform
- manage_agent_knowledge — manage which boards/docs this agent has access to

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): "create" — create a new agent via AI (pass prompt). "create_blank" — create a new agent manually (pass name/role/etc). "get" — fetch one agent by agent_id or list owned agents. "update" — modify mutable fields on an existing agent. "delete" — permanently delete an agent (irreversible). "activate" — transition agent to ACTIVE. "deactivate" — transition agent to INACTIVE. "run" — manually enqueue an agent run (fire-and-forget). One of: `create`, `create_blank`, `get`, `update`, `delete`, `activate`, `deactivate`, `run`.
- `agent_id` (`string`, optional): Used with action:"get" to fetch a specific agent. Required for action:"update", "delete", "activate", "deactivate", "run". Omit for action:"create", "create_blank", or action:"get" (to list owned agents).
- `agent_model` (`string`, optional): Used with action:"create" or action:"update". Omit unless the user explicitly names a valid monday-supported model. One of: `CLAUDE_FABLE_5`, `CLAUDE_OPUS_4_7`, `CLAUDE_SONNET_4_6`, `GEMINI_2_5_FLASH`, `GPT_5_2`.
- `avatar_url` (`string`, optional): Used with action:"create_blank". HTTPS URL of the avatar. Prefer dapulse-res.cloudinary.com or cdn.monday.com.
- `background_color` (`string`, optional): Used with action:"create_blank". Lowercase hex, e.g. "#9450fd".
- `gender` (`string`, optional): Used with action:"create_blank". Hint for generated avatar/name when profile fields are omitted. One of: `male`, `female`.
- `name` (`string`, optional): Used with action:"create_blank" or action:"update". Display name of the agent.
- `plan` (`string`, optional): Used with action:"update". New step-by-step execution plan in markdown.
- `prompt` (`string`, optional): Required for action:"create". Plain-language description of what the agent should do. Platform generates profile, goal, and plan via AI.
- `role` (`string`, optional): Used with action:"create_blank" or action:"update". Short role title (e.g. "Customer Success Bot").
- `role_description` (`string`, optional): Used with action:"create_blank" or action:"update". Detailed description of the agent role.
- `user_prompt` (`string`, optional): Used with action:"create_blank". Stored as metadata. Not used for AI generation.

Example input: `{"action":"create"}`

### `mondaymcp_manageautomations`

ManageAutomations · Destructive

Activate, deactivate, or delete an existing monday.com automation.

Requires an automation id. When the user refers to an automation by name, always call list_automations first to resolve the id — never guess or infer ids.

Actions:
- activate: enables a paused automation so it starts responding to its trigger.
- deactivate: pauses an automation while preserving its definition.
- delete: permanently removes an automation — irreversible.

When intent is ambiguous ("stop", "turn off", "pause"), prefer deactivate over delete.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `action` (`string`, required): The operation to perform. activate: enables a paused automation so it responds to its trigger. deactivate: pauses an automation without deleting it. delete: permanently removes an automation (irreversible). One of: `activate`, `deactivate`, `delete`.
- `workflowId` (`string`, required): The automation ID to operate on. Obtain from list_automations.

Example input: `{"action":"activate","workflowId":"<workflowId>"}`

### `mondaymcp_runaction`

Run Action · Destructive

Execute a saved action by ID. Optionally pass variables (injected as environment variables, access via os.environ).

Example:
  id: "abc-123", vars: {"board_id": 12345, "limit": 5}

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): Action ID
- `vars` (`object`, optional): Variables injected as environment variables into the sandbox (access via os.environ / process.env)

Example input: `{"id":"<id>"}`

### `mondaymcp_updateaction`

Update Action · Destructive

Update an existing action. Only pass the fields you want to change.

Example:
  id: "550e8400-e29b-41d4-a716-446655440000", name: "Updated name", code: "print('new code')"

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): Action ID
- `code` (`string`, optional): New source code (max 1 MB)
- `description` (`string`, optional): New description — short summary: what data the code accesses (specific boards/items by name or ID, or scope if broad), what processing it performs, and how the result is returned. Max 255 characters.
- `language` (`string`, optional): New programming language — one of: javascript, typescript, python. One of: `javascript`, `typescript`, `python`.
- `name` (`string`, optional): New short, descriptive action name
- `output_description` (`string`, optional): New instructions describing what should be done with the execution output, max 2000 characters.
- `vars_schema` (`array`, optional): New variable definitions

Example input: `{"id":"<id>"}`

### `mondaymcp_updatedoc`

UpdateDoc · Destructive

Update an existing monday.com document. Provide doc_id (preferred) or object_id, plus an ordered operations array (executed sequentially, stops on first failure).

OPERATIONS:
- set_name: Rename the document.
- add_markdown_content: Append markdown as blocks (or insert after a block). Best for text, headings, lists, simple tables — no block IDs needed.
- update_block: Update content of an existing text, code, or list_item block in-place.
- create_block: Create a new block at a precise position. Use parent_block_id to nest inside notice_box, table cell, or layout cell.
- delete_block: Remove any block. The ONLY option for BOARD, WIDGET, DOC embed, and GIPHY blocks.
- replace_block: Delete a block and create a new one in its place (use when update_block is not supported).
- add_comment: Create a new comment or reply on the document (doc-level, block-level, or text-selection).

WHEN TO USE EACH OPERATION:
- text / code / list_item → update_block. Use replace_block to change subtype (e.g. NORMAL_TEXT→LARGE_TITLE)
- divider / table / image / video / notice_box / layout → replace_block (properties immutable after creation)
- BOARD / WIDGET / DOC / GIPHY → delete_block only

GETTING BLOCK IDs: Call read_docs with include_blocks: true — returns id, type, position, and content per block.

BLOCK CONTENT (delta_format): Array of insert ops. Last op MUST be {insert: {text: "\n"}}.
- Plain: [{insert: {text: "Hello"}}, {insert: {text: "\n"}}]
- Bold: [{insert: {text: "Hi"}, attributes: {bold: true}}, {insert: {text: "\n"}}]
- Mention user/doc/board: [{insert: {text: "Hey "}}, {insert: {mention: {id: 12345, type: "USER"}}}, {insert: {text: "\n"}}] — type is USER, DOC, or BOARD. id is numeric (user IDs from list_users_and_teams)
- Inline column value: [{insert: {column_value: {item_id: 111, column_id: "status"}}}, {insert: {text: "\n"}}]
- Supported attributes: bold, italic, underline, strike, code, link, color, background (not applicable to mention/column_value ops)

IMAGE WITH ASSET: For asset-based images, use create_block with block_type "image" and asset_id (instead of public_url). add_markdown_content does NOT support asset images — for mixed content, alternate add_markdown_content (text) and create_block (image) operations in sequence.

COMMENTS:
- add_comment: Create a new comment or reply on the document. Three scopes:
  - Doc-level (no block_id): comment appears on the doc as a whole.
  - Block-level (block_id only): comment is anchored to a specific block. The block shows a comment indicator in the UI.
  - Text-selection (block_id + selection_from + selection_length): comment is anchored to a specific character range inside a text/code/list_item block. That text is highlighted with a comment marker.
  Block-level and text-selection comments only work on blocks with text content (text, code, list_item, title, quote). They do NOT work on: divider, page_break, table, layout, notice_box, image, video, or giphy blocks.
  Get block IDs from read_docs with include_blocks: true. Format body with HTML, not markdown. Use mentions_list for @mentions.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `operations` (`array`, required): Ordered list of operations to perform. Executed sequentially. Stops at first failure.

Operation types:
- set_name: Rename the document.
- add_markdown_content: Append markdown as blocks (simplest for text/lists/tables).
- update_block: Change content of an existing text/code/list/divider block.
- create_block: Create a new block at a specific position (supports text, list_item, code, divider, page_break, image, video, notice_box, table, layout).
- delete_blocks: Permanently delete 1–100 blocks in one call. Provide all block IDs in the block_ids array. Works for all block types including BOARD, WIDGET, DOC embed, and GIPHY.
- replace_block: Delete a block and create a new one in its place. Use for: changing image/video source, table restructure, notice_box theme change.
- add_comment: Create a new comment or reply on the document. Use parent_update_id to reply to an existing comment. Format text with HTML. Uses the doc's backing board item.

WHEN TO USE WHICH:
- Adding new text sections → add_markdown_content
- Adding asset-based images → create_block with block_type "image" and asset_id (add_markdown_content does NOT support asset images)
- Mixed content with asset images → alternate add_markdown_content (for text) and create_block (for each image) in sequence
- Editing existing text block → update_block
- Changing an image URL → replace_block (image URL is immutable after creation)
- Changing video URL → replace_block
- Restructuring a table → replace_block
- BOARD/WIDGET/DOC/GIPHY blocks → delete_block only (no public API to create these)

NESTING CONTENT IN CONTAINERS:
- notice_box: Fully supported. Create the notice_box first, then in a separate call create child blocks with parent_block_id set to the notice_box ID. You cannot reference a block ID created in the same call.
- table: Cell-level API nesting is NOT supported. To create a table with content, use add_markdown_content with a markdown table (e.g. "| H1 | H2 |\n| --- | --- |\n| A | B |"). This creates a pre-populated table in one shot. Empty tables created via create_block cannot have their cells populated through the API.
- layout: Cell-level API nesting is NOT supported and there is no markdown equivalent. Layouts can only be created empty via create_block. No workaround exists to populate layout columns through the API.
Deleting a container does NOT delete its children — delete children first for clean removal.

Block IDs are available in the blocks array returned by read_docs.
- `doc_id` (`string`, optional): The document ID (the id field from read_docs). Takes priority over object_id if both are provided.
- `object_id` (`string`, optional): The document object ID (the object_id field from read_docs, visible in the document URL). Resolved to doc_id.

Example input: `{"operations":[]}`

### `mondaymcp_vibedelete`

VibeDelete · Destructive

Delete a Vibe app and its associated assets. Destructive.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `app_id` (`integer`, required): Internal Vibe app id

Example input: `{"app_id":1}`

## Workflows

### Get items from a board

Use `mondaymcp_getboarditemspage` to fetch items from a monday.com board. You need the board's numeric ID, which you can find in the board URL (`https://mycompany.monday.com/boards/<BOARD_ID>`).

> note: Find your board ID
>
> Open the board in monday.com and look at the URL. The number after `/boards/` is the board ID. You can also call `mondaymcp_search` with `searchType: 'BOARD'` and a `searchTerm` to discover board IDs programmatically.

  **Node.js**

  ```typescript
  const items = await actions.executeTool({
    connector: 'mondaymcp',
    identifier: 'user_123',
    toolName: 'mondaymcp_getboarditemspage',
    toolInput: {
      boardId: 1234567890,
      limit: 50,
    },
  });
  console.log(items);
  ```

  **Python**

  ```python
  items = actions.execute_tool(
      connection_name="mondaymcp",
      identifier="user_123",
      tool_name="mondaymcp_getboarditemspage",
      tool_input={
          "boardId": 1234567890,
          "limit": 50,
      },
  )
  print(items)
  ```

### Create an item and add an update

Use `mondaymcp_createitem` to add a new item to a board, then `mondaymcp_createupdate` to post a comment or status update on it.

  **Node.js**

  ```typescript
  // Step 1 — create the item
  const newItem = await actions.executeTool({
    connector: 'mondaymcp',
    identifier: 'user_123',
    toolName: 'mondaymcp_createitem',
    toolInput: {
      boardId: 1234567890,
      name: 'Fix login bug',
      columnValues: '{}',
      groupId: 'topics',
    },
  });
  const itemId = newItem.id;

  // Step 2 — post an update on the item
  await actions.executeTool({
    connector: 'mondaymcp',
    identifier: 'user_123',
    toolName: 'mondaymcp_createupdate',
    toolInput: {
      itemId,
      body: 'Assigned to the auth team. Expected fix in next sprint.',
    },
  });
  ```

  **Python**

  ```python
  # Step 1 — create the item
  new_item = actions.execute_tool(
      connection_name="mondaymcp",
      identifier="user_123",
      tool_name="mondaymcp_createitem",
      tool_input={
          "boardId": 1234567890,
          "name": "Fix login bug",
          "columnValues": "{}",
          "groupId": "topics",
      },
  )
  item_id = new_item["id"]

  # Step 2 — post an update on the item
  actions.execute_tool(
      connection_name="mondaymcp",
      identifier="user_123",
      tool_name="mondaymcp_createupdate",
      tool_input={
          "itemId": item_id,
          "body": "Assigned to the auth team. Expected fix in next sprint.",
      },
  )
  ```

### Update column values on an item

Use `mondaymcp_changeitemcolumnvalues` to set structured column data — such as status, date, or assignee — on an existing item.

  **Node.js**

  ```typescript
  await actions.executeTool({
    connector: 'mondaymcp',
    identifier: 'user_123',
    toolName: 'mondaymcp_changeitemcolumnvalues',
    toolInput: {
      boardId: 1234567890,
      itemId: 9876543210,
      // Column values are JSON-encoded per the monday.com column type
      columnValues: JSON.stringify({
        status: { label: 'In Progress' },
        date4: { date: '2025-08-01' },
      }),
    },
  });
  ```

  **Python**

  ```python
  import json

  actions.execute_tool(
      connection_name="mondaymcp",
      identifier="user_123",
      tool_name="mondaymcp_changeitemcolumnvalues",
      tool_input={
          "boardId": 1234567890,
          "itemId": 9876543210,
          # Column values are JSON-encoded per the monday.com column type
          "columnValues": json.dumps({
              "status": {"label": "In Progress"},
              "date4": {"date": "2025-08-01"},
          }),
      },
  )
  ```

### Search across monday.com

Use `mondaymcp_search` to find boards, items, docs, or workspaces by keyword.

  **Node.js**

  ```typescript
  const results = await actions.executeTool({
    connector: 'mondaymcp',
    identifier: 'user_123',
    toolName: 'mondaymcp_search',
    toolInput: {
      searchTerm: 'Q3 roadmap',
      searchType: 'BOARD',
    },
  });
  console.log(results);
  ```

  **Python**

  ```python
  results = actions.execute_tool(
      connection_name="mondaymcp",
      identifier="user_123",
      tool_name="mondaymcp_search",
      tool_input={
          "searchTerm": "Q3 roadmap",
          "searchType": "BOARD",
      },
  )
  print(results)
  ```

## Related

Other ways to connect Monday.com:

- [OAuth](/agentkit/connectors/monday/): Scalekit connector, OAuth, 73 tools

Other Project Management connectors ([all 31](/agentkit/connectors/?category=project-management)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 62 tools
- [Airtable](/agentkit/connectors/airtable/): Scalekit connector, OAuth, 26 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |