monday.com

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

create_form

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

create_group

Create a single item or subitem on a monday.com board, or duplicate an existing item. [IMPORTANT] If you need to create multiple items in one call, use create_items instead of calling this tool in a loop. Otherwise: 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 with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.

create_item

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 with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.

create_items

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.

create_notification

Create a new table-type board view with optional filters, sort, tags, and table-specific settings including conditional coloring (highlight rows/cells based on column values). CONDITIONAL COLORING: Use settings.conditional_coloring to highlight rows or cells. Each rule specifies a column_id, operator, value (human-readable — e.g. "Stuck", not an index), color, and entire_row flag. Example: highlight rows where Status is "Stuck" in red, or where Salary > 100000 in green. Use this tool instead of create_view when you need table-specific settings like column visibility, group-by, or conditional coloring. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

create_view_table

Create a new structured activity entry (call, meeting, email) on a CRM item's timeline. Create a new structured activity entry on a CRM item's timeline. Returns the created timeline_item_id. For freeform notes (meeting outcomes, follow-ups), use create-timeline-note instead.

create-timeline-item

Add an unstructured note (meeting outcome, follow-up reminder, or rep context) to a CRM item's timeline. Log a freeform text note on a CRM item's timeline — meeting outcomes, follow-up reminders, context for the next rep, or any unstructured observation.

create-timeline-note

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.

create_update

Create a new board view (tab) with optional filters and sorting. Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text View types: TABLE (standard board), DASHBOARD, FORM, APP

create_view

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

create_widget

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.

create_form_submission

Creates a new empty workflow in the given workspace and returns its identifiers (workflowObjectId and workflowDraftId). Use this tool when the user wants to start a brand-new workflow from scratch, rather than modifying an existing one. Only the workspace is required; title, privacy kind, description, folder, and owners are optional and fall back to sensible defaults. The tool returns a JSON object with the identifiers of the newly created workflow, which can then be used with the other workflow tools. To build a URL to the workflow, use the template: https://<account_slug>.monday.com/custom_objects/<workflowObjectId>. To get a real URL example of the account, call the monday GraphQL MCP tool with the query `{ me { url } }`.

create_workflow

Create a new workspace in monday.com

create_workspace

Create a new outreach sequence on a board. Create a new sequence on a board. Always created INACTIVE; use `activate-sequence` to enable it before the sequence can run. Call this tool directly with whatever arguments you have — do not pre-fetch boards or email accounts first. Never set ordinals or UUIDs. Never fabricate steps.

create-sequence

Deactivate a sequence so it stops accepting new enrollments. Deactivate a sequence (sets status to INACTIVE, blocking new enrollments while existing enrollments continue). Convenience alias for update-sequence-status when direction is known to be INACTIVE.

deactivate-sequence

Use to permanently delete a saved action by its ID. Delete a saved action. Example: id: "550e8400-e29b-41d4-a716-446655440000"

delete_action

Delete a board view (tab) from a monday.com board. Use get_board_info to find the view ID before deleting.

delete_view

Copy an existing sequence, including its steps, as a new INACTIVE sequence. Duplicate a sequence. Creates a copy with the same steps and configuration. The new sequence starts with INACTIVE status.

duplicate-sequence

Enroll one or more CRM contacts or leads into an outreach sequence. The sequence must be active. Returns per-item success/failure so partial failures do not silently drop contacts.

enroll-item-in-sequence

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

execute_code

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.

explore_meetings

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.

finalize_asset_upload

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

form_questions_editor

Retrieve a saved action by ID. Example: id: "550e8400-e29b-41d4-a716-446655440000"

get_action

Fetch aggregated CRM activity stats: call counts and durations grouped by rep, activity type, or item. Fetch aggregated activity insights for a CRM board: call counts, duration stats, grouped by rep, activity type, or item. Does not return individual activity records.

get-activity-insights

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.

all_widgets_schema

Get a presigned URL to upload a file to monday.com. Returns an upload_id and upload_url. Only call this tool if you can execute a direct HTTP PUT with binary file data and read response headers (e.g. via shell/curl). If you can't, tell the user direct file upload isn't supported here — don't call this tool. 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.

get_asset_upload_url

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.

get_assets

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".

get_automation_runs

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.

get_automation_statistics

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. [REQUIRED PRECONDITION]: Call this with includeData=true before undo_action — it is the source of the action_record_uuid that identifies the action to undo.

get_board_activity

Get comprehensive board information including metadata, structure, owners, and configuration. Also returns generated board knowledge when available, including human-readable business context, workflow and status meanings, column purposes, people roles, and related boards. Knowledge is best-effort and may be null while it is unavailable or still being generated. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object. On large boards, ALWAYS narrow the response: use filters.views.names or filters.views.ids when you only need specific views, and/or filters.columns.ids when you only need specific columns. Set filters.views.only or filters.columns.only when you want just that section — full views[].settings across many views can be multi-MB. The response includes hierarchy_type which indicates if the board is a multi-level board ("multi_level") where items can have nested subitems up to 5 levels deep on the same board. On multi-level boards, subitems share the same columns as parent items and subItemColumns will be null. Call this FIRST whenever you are not already familiar with a board structure (column IDs, column types, column revisions, status labels) — before reading or writing its data, or before any tool that declares this as a required precondition (e.g. get_board_items_page, board_insights, create_item, create_items, update_items, change_item_column_values, update_column, create_view, create_view_table, update_view, update_view_table). Also use the views it returns to resolve a view referenced by name (pass that name in filters.views.names), and as the source of view ids for update_view and update_view_table. Each column's "settings" field is the raw API value for that existing column, shown so you can read current labels/config — it is NOT the format expected by the columnSettings parameter of create_column or update_column. Never copy a column's "settings" object verbatim into columnSettings — use get_column_type_info with fetchMode "schema" to get the correct shape for the column type you are creating or updating.

get_board_info

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 with filters.columns.only to get column metadata without fetching views. 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.

board_insights

Get items from a monday.com board: list, filter, sort, search and paginate board items with their column values, groups, subitems and item descriptions. Returns structured JSON with board info (id, name, hierarchy_type), item details (id, name, url, created_at, updated_at, parent_item_id) and pagination (has_more, nextCursor, count). Use nextCursor from the response as cursor to get the next page while has_more is true. Filters, orderBy, itemIds and searchTerm are encoded in the cursor and ignored on cursor pages. [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 with filters.columns.only to get column metadata without fetching views. Column ids are board-specific and are needed for filters, orderBy and columnIds. [FILTERS]: Each rule is {columnId, operator, compareValue} and optionally compareAttribute; filtersOperator ("and" by default) joins them. Before building a rule, call get_column_type_info with fetchMode "guidelines" for that column's type and follow data.guidelines.filter - the operator and the compareValue shape depend on the column type, and a wrong shape is rejected, not ignored. Invalid filters are rejected server-side with a structured error naming the offending rule and field, so check the guidelines first rather than guessing an operator. [VIRTUAL COLUMNS]: Four filterable and sortable columns exist that get_board_info never returns - "group" (the item's board group; the group id goes in compareValue), "__creation_log__" (creation time), "__last_updated__" (update time) and "__item_id__" (item id). All four are also valid in orderBy, e.g. "__creation_log__" with direction "desc" to sort newest-first. Their column types for get_column_type_info are not the ids: use columnType "group", "item_id", "creation_log" and "last_updated" respectively to get each one's compareValue and operator rules. [PAGE SIZE]: limit accepts up to 2000 items per page (default 25), so a large board can be read in far fewer calls than the previous 500 cap allowed. Ask for what you need: a bigger page costs one round trip but a larger response, and the few requests answered by the monday API (see the routing notes above) come back with 500 items, a cursor and a warning. [SEARCH]: Use searchTerm for vague or approximate wording (e.g. "marketing campaign"); use filters when the user gives an exact value for a specific column. [ITEM DESCRIPTION]: To retrieve an item description (the rich-text body/details of a monday.com item), set includeItemDescription to true - the response includes the description document blocks with their content, type and id. Use this whenever the user asks about an item description, body, details, or notes. [MULTI-LEVEL BOARDS]: The response includes hierarchy_type on the board ("multi_level" for MLS boards) and parent_item_id on each item. On multi-level boards items form a tree (up to 5 levels). Use includeSubItems to get descendants (each carrying parent_item_id to reconstruct the tree). Top-level items have no parent_item_id. [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 with filters.views.names set to that view name (avoids downloading all views on large boards), extract the matching view's filter field, then pass it as the filters argument here.

get_board_items_page

Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — to understand structure, validation rules, and available properties for column settings. Call this BEFORE any tool that writes column settings: create_column, update_column, and manage_object_schema_columns. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation (no schema, no GraphQL round-trip). Call this before building any filter rule that uses compare_value/operator for that column type — e.g. get_board_items_page, board_insights, or a view's filters (create_view, create_view_table, update_view, update_view_table) — and before building board insights aggregation counts.

get_column_type_info

List the custom activity types (e.g. Demo, Site Visit) available for structured CRM timeline entries. List the custom activity types available for logging on the CRM timeline. Each type has an opaque `id` (a UUID-like string) and a human-readable `name` (e.g. "Demo", "Site Visit"). When creating a structured timeline entry via create-timeline-item, pass the `id` value — not the `name` — as custom_activity_id.

get-custom-activities

Get a monday.com form by its form token, including its pages, questions, question ids, settings, and conditional showIfRules. 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. Call this FIRST before any tool that acts on an existing form: create_form_submission (to know the questions and their constraints), form_questions_editor (to resolve question ids and current structure), and update_form (to see the current settings before changing them).

get_form

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.

get_graphql_schema

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.

get_meetings_content