monday.com is a work management platform for organizing projects, workflows, and customer processes in boards, docs, and dashboards. It helps teams plan work, track progress, and collaborate across functions.
monday.com is a work management platform for organizing projects, workflows, and customer processes in boards, docs, and dashboards. It helps teams plan work, track progress, and collaborate across functions. On Nagent, Monday MCP is exposed as a fully-configurable productivity & project management integration that any agent can call — 23 actions, and DCR_OAUTH authentication. No code is required to wire Monday MCP into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Monday MCP to automate the kinds of tasks productivity & project management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Monday MCP into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Monday MCP, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MONDAY_MCP_ALL_MONDAY_APIExecute 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.
Input parameters
Custom GraphQL query/mutation. you need to provide the full query / mutation
JSON string containing the variables for the GraphQL operation
MONDAY_MCP_ALL_WIDGETS_SCHEMAFetch 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.
MONDAY_MCP_BOARD_INSIGHTSThis 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.
Input parameters
The limit of the results
The id of the board to get insights for
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.
The columns to group by. All columns in the group by must be in the aggregations as well without a function.
The columns to order by, will control the order of the items in the response
The aggregations to get. Before sending the aggregations, use get_board_info tool to check "aggregationGuidelines" key for information. Transformative functions and plain columns (no function) must be in group by. \[REQUIRED PRECONDITION\]: Either send this field or the stringified version of it.
The logical operator to use for the filters
**ONLY FOR MICROSOFT COPILOT**: The filters to apply on the items. Send this as a stringified JSON array of "filters" field. Read "filters" field description for details how to use it.
**ONLY FOR MICROSOFT COPILOT**: The order by to apply on the items. Send this as a stringified JSON array of "orderBy" field. Read "orderBy" field description for details how to use it.
**ONLY FOR MICROSOFT COPILOT**: The aggregations to get. Send this as a stringified JSON array of "aggregations" field. Read "aggregations" field description for details how to use it.
MONDAY_MCP_CHANGE_ITEM_COLUMN_VALUESChange the column values of an item in a monday.com board
Input parameters
The ID of the item to be updated
The ID of the board that contains the item to be updated
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\\"}"
MONDAY_MCP_CREATE_BOARDCreate a monday.com board
Input parameters
The kind of board to create
The name of the board to create
The ID of the workspace to create the board in
The description of the board to create
MONDAY_MCP_CREATE_COLUMNCreate a new column in a monday.com board
Input parameters
The id of the board to which the new column will be added
The type of the column to be created
The title of the column to be created
Column-specific configuration settings as a JSON string. Use the get_column_type_info tool to fetch the JSON schema for the given column type.
The description of the column to be created
MONDAY_MCP_CREATE_DASHBOARDUse 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
Input parameters
Visibility level: PUBLIC or PRIVATE
Human-readable dashboard title (UTF-8 chars)
List of board IDs as strings (min 1 element)
ID of the workspace that will own the dashboard
Optional folder ID within workspace to place this dashboard (if not provided, dashboard will be placed in workspace root)
MONDAY_MCP_CREATE_DOCCreate 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) - item: Creates a document attached to an item (requires item_id, optional column_id) USAGE EXAMPLES: - Workspace doc: { location: "workspace", workspace_id: 123, doc_kind: "private" , markdown: "..." } - Workspace doc in folder: { location: "workspace", workspace_id: 123, folder_id: 17264196 , markdown: "..." } - Item doc: { location: "item", item_id: 456, column_id: "doc_col_1" , markdown: "..." }
Input parameters
\[REQUIRED - use only when location="item"\] Item ID to attach the new document to
\[OPTIONAL - use only when location="workspace"\] Document kind (public/private/share). Defaults to public.
Name for the new document.
Location where the document should be created - either in a workspace or attached to an item
Markdown content that will be imported into the newly created document as blocks.
\[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.
\[OPTIONAL - use only when location="workspace"\] Optional folder ID to place the document inside a specific folder
\[REQUIRED - use only when location="workspace"\] Workspace ID under which to create the new document
MONDAY_MCP_CREATE_FOLDERCreate a new folder in a monday.com workspace
Input parameters
The name of the folder to be created
The color of the folder
The custom icon of the folder
The font weight of the folder
The ID of the workspace where the folder will be created
The ID of the parent folder
MONDAY_MCP_CREATE_FORMCreate a monday.com form. This will create a new form as well as a new board for which the form’s responses will be stored. The returned board_id is the ID of the board that was created while the returned formToken can be used for all future queries and mutations to continue editing the form.
Input parameters
The board kind to create for the board in which the form will create items in.
Array of user IDs who will have owner permissions on the board in which the form will create items in.
The name of the board that will be created to store the form responses in.
Array of team IDs whose members will have owner permissions on the board in which the form will create items in.
Array of user IDs who will receive notifications about board activity for the board in which the form will create items in.
The folder in which the form will be created under.
The name of the folder in which the form will be created in.
The workspace in which the form will be created in.
Array of team IDs whose members will receive notifications about board activity for the board in which the form will create items in.
MONDAY_MCP_CREATE_GROUPCreate 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
Input parameters
The ID of the board to create the group in
The name of the new group (maximum 255 characters)
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
The ID of the group to position this new group relative to
Whether to position the new group before or after the relativeTo group
MONDAY_MCP_CREATE_ITEMCreate 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.
Input parameters
The name of the new item to be created, must be relevant to the user's request
The id of the board to which the new item will be added
The id of the group id to which the new item will be added, if its not clearly specified, leave empty
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\\"}"
The id of the parent item under which the new subitem will be created
The id of existing item to duplicate and update with new values (only provide when duplicating)
MONDAY_MCP_CREATE_UPDATECreate 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.
Input parameters
The update text to be created. Do not use @ to mention users, use the mentionsList field instead.
The id of the item to which the update will be added
Optional JSON array of mentions in the format: \[{"id": "123", "type": "User"}, {"id": "456", "type": "Team"}\]. Valid types are: User, Team, Board, Project
MONDAY_MCP_CREATE_WIDGETCreate 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
Input parameters
Widget-specific settings as JSON object conforming to widget schema. Use all_widgets_schema tool to get the required schema for each widget type.
Type of widget to create: i.e CHART, NUMBER, BATTERY
Widget display name (1-255 UTF-8 chars)
ID of the parent container (dashboard ID or board view ID)
**ONLY FOR MICROSOFT COPILOT**: The settings object. Send this as a stringified JSON of "settings" field. Read "settings" field description for details how to use it.
Type of parent container: DASHBOARD or BOARD_VIEW
MONDAY_MCP_CREATE_WORKSPACECreate a new workspace in monday.com
Input parameters
The name of the new workspace to be created
The description of the new workspace
The kind of workspace to create
The account product ID associated with the workspace
MONDAY_MCP_FORM_QUESTIONS_EDITORCreate, update, or delete a question in a monday.com form
Input parameters
The type of operation to perform on the question. Can delete, update, or create. When updating or deleting a question, the questionId is required. When creating or updating a question, the question object is required. When updating, the question is a patch object, meaning that only the fields that are provided will be updated.
The question object containing all properties for creation or update. When creating a question, the title is required.
The unique identifier token for the form. Required for all form-specific operations.
The unique identifier for the question. Used to target specific questions within a form.
**ONLY FOR MICROSOFT COPILOT**: The question object. Send this as a stringified JSON of "question" field. Read "question" field description for details how to use it.
MONDAY_MCP_GET_BOARD_ACTIVITYGet board activity logs for a specified time range (defaults to last 30 days)
Input parameters
End date for activity range (ISO8601DateTime format). Defaults to now
The id of the board to get activity for
Start date for activity range (ISO8601DateTime format). Defaults to 30 days ago
MONDAY_MCP_GET_BOARD_INFOGet comprehensive board information including metadata, structure, owners, and configuration
Input parameters
The id of the board to get information for
MONDAY_MCP_GET_BOARD_ITEMS_PAGEGet all items from a monday.com board with pagination support and optional column values. 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.\[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.
Input parameters
The number of items to get
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
The id of the board to get items from
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.
The ids of the items to get. The count of items should be less than 100.
The columns to order by, will control the order of the items in the response
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
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.
The number of sub items to get per item. This is only used when includeSubItems is true.
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.
The operator to use for the filters
Whether to include sub items in the response. PERFORMANCE OPTIMIZATION: Only set this to true when you actually need the sub items data.
**ONLY FOR MICROSOFT COPILOT**: The filters to apply on the items. Send this as a stringified JSON array of "filters" field. Read "filters" field description for details how to use it.
**ONLY FOR MICROSOFT COPILOT**: The order by to apply on the items. Send this as a stringified JSON array of "orderBy" field. Read "orderBy" field description for details how to use it.
MONDAY_MCP_GET_COLUMN_TYPE_INFORetrieves comprehensive information about a specific column type, including JSON schema definition and other metadata. Use this before creating columns with the create_column tool to understand the structure, validation rules, and available properties for column settings.
Input parameters
The column type to retrieve information for (e.g., "text", "status", "date", "numbers")
MONDAY_MCP_GET_FORMGet 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 token is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the token is abc123def456ghi789.
Input parameters
The unique identifier token for the form. Required for all form-specific operations.
MONDAY_MCP_GET_GRAPHQL_SCHEMAFetch 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.
Input parameters
Type of operation: "read" for queries, "write" for mutations
Dummy parameter for no-parameter tools
MONDAY_MCP_GET_MONDAY_DEV_SPRINTS_BOARDSDiscover monday-dev sprints boards and their associated tasks boards in your account.
No publicly available marketplace agent is found using this tool yet. There are 71 agents privately built on Nagent that already use Monday MCP.
Build on Nagent
Connect Monday MCP to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Monday MCP, and click "Connect Now." You'll authenticate with DCR_OAUTH — Nagent handles credential storage and refresh automatically. Once connected, Monday MCP is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Monday MCP is connected, you configure its 23 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Monday MCP steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Monday MCP event fires, the agent kicks off automatically.
Every Monday MCP action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Monday MCP ships with 23 pre-built productivity & project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Monday MCP together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Monday MCP-based workflows tailored to your business.