Monday MCP

Overview

monday.com is a work management platform for organizing projects, workflows, and customer processes in boards, docs, and dashboards. With the SquadOS integration, your agents can create and update items, manage boards, author documents, track development sprints, and execute any monday.com API operation via GraphQL.

• Official website: https://monday.com/
• Composio documentation: docs.composio.dev/toolkits/monday_mcp

Authentication

This tool uses OAuth 2.0 with Dynamic Client Registration (DCR_OAUTH) to connect.

Since a Composio-managed app is not available for this integration, you need to create a developer app on monday.com and provide your own OAuth credentials.

You will need the following fields:

Field	Required	Description
client_id	Yes	OAuth client ID generated when creating an app in the monday.com developer portal.
client_secret	Yes	OAuth client secret generated alongside the Client ID in the monday.com developer portal.

How to get credentials

1. Go to monday.com/developers/apps, log in, and click Create App.
2. Give the app a name (e.g., Composio-Monday) and save.
3. Copy the Client ID and Client Secret that are auto-generated — store them securely.
4. In the Redirect URLs section, add the following callback URL (no trailing slash): https://backend.composio.dev/api/v3/toolkits/auth/callback
5. In the OAuth Scopes section, add the required scopes, for example: boards:read, boards:write, items:read, items:write, users:read, docs:read, docs:write, updates:read, updates:write, workspaces:read, workspaces:write
6. Save the app. You will use the Client ID and Client Secret when configuring the connection in Composio.

Tip

Store the Client Secret securely — monday.com does not display it again after the creation screen is closed.

How to connect in SquadOS

1. Go to Tools in the side menu (/admin/tools).
2. Open the Available tab and search for Monday MCP.
3. Click the card to open the details modal and hit Connect.
4. You’re taken to the secure connection page hosted by Composio, where you enter the Client ID and Client Secret obtained above and authorize access via OAuth.
5. Once done, you’re sent back to SquadOS with the account connected and the tool available to your agents. (Connection-flow details in Organization Tools.)

Available actions

All monday api

MONDAY_MCP_ALL_MONDAY_API

Execute any monday.com API operation by generating GraphQL queries and mutations dynamically. Make sure you ask only for the fields you need. Use get_graphql_schema and get_type_details first to understand the schema before crafting your query.

Input parameters

Name	Type	Required	Description
query	string	Yes	Custom GraphQL query/mutation. You need to provide the full query/mutation.
variables	string	Yes	JSON string containing the variables for the GraphQL operation.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

All widgets schema

MONDAY_MCP_ALL_WIDGETS_SCHEMA

Fetch complete JSON Schema 7 definitions for all available widget types in monday.com. Use before creating widgets to understand required fields, data types, and validation rules for each widget type.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Board insights

MONDAY_MCP_BOARD_INSIGHTS

Calculate insights about a board’s data by filtering, grouping, and aggregating columns. Use to get summaries such as total item count, count by status, or count by column. Use get_board_info first if you are not familiar with the board structure.

Input parameters

Name	Type	Required	Description
boardId	number	Yes	The ID of the board to get insights for.
limit	number	No	The limit of the results.
filters	array	No	Filter configuration to apply on items. Check get_board_info for filtering guidelines per column.
groupBy	array	No	Columns to group by. All columns in the group by must also be in aggregations.
orderBy	array	No	Columns to order the results by.
aggregations	array	No	Aggregations to calculate. Check get_board_info for guidelines.
filtersOperator	string ("and" or "or")	No	Logical operator to use for the filters.
filtersStringified	string	No	ONLY FOR MICROSOFT COPILOT: filters as a stringified JSON array of the filters field.
orderByStringified	string	No	ONLY FOR MICROSOFT COPILOT: order by as a stringified JSON array of the orderBy field.
aggregationsStringified	string	No	ONLY FOR MICROSOFT COPILOT: aggregations as a stringified JSON array of the aggregations field.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Change item column values

MONDAY_MCP_CHANGE_ITEM_COLUMN_VALUES

Change the column values of an item in a monday.com board.

Input parameters

Name	Type	Required	Description
itemId	number	Yes	The ID of the item to be updated.
boardId	number	Yes	The ID of the board that contains the item.
columnValues	string	Yes	String with the new column values in format {"column_id": "value", ...}. For status use {"label": "Done"}; for date use {"date": "2023-05-25"}.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create board

MONDAY_MCP_CREATE_BOARD

Create a monday.com board.

Input parameters

Name	Type	Required	Description
boardName	string	Yes	The name of the board to create.
boardKind	string ("private", "public", or "share")	No	The visibility kind of the board.
workspaceId	string	No	The ID of the workspace to create the board in.
boardDescription	string	No	The description of the board.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create column

MONDAY_MCP_CREATE_COLUMN

Create a new column in a monday.com board.

Input parameters

Name	Type	Required	Description
boardId	number	Yes	The ID of the board to which the new column will be added.
columnType	string	Yes	The type of the column (e.g., "text", "status", "date", "numbers", "people", "timeline", and others).
columnTitle	string	Yes	The title of the column to be created.
columnSettings	string	No	Column-specific configuration settings as a JSON string. Use get_column_type_info to fetch the schema for the given type.
columnDescription	string	No	The description of the column.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create dashboard

MONDAY_MCP_CREATE_DASHBOARD

Create a new monday.com dashboard that aggregates data from one or more boards. Use to create data visualizations and widget containers.

Input parameters

Name	Type	Required	Description
name	string	Yes	Human-readable dashboard title (UTF-8 chars).
board_ids	array	Yes	List of board IDs as strings (min 1 element).
workspace_id	string	Yes	ID of the workspace that will own the dashboard.
kind	string ("PRIVATE" or "PUBLIC")	No	Visibility level of the dashboard.
board_folder_id	string	No	Optional folder ID within the workspace. If not provided, the dashboard is placed in the workspace root.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create doc

MONDAY_MCP_CREATE_DOC

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.

Input parameters

Name	Type	Required	Description
doc_name	string	Yes	Name for the new document.
location	string ("workspace" or "item")	Yes	Location where the document should be created: in a workspace or attached to an item.
markdown	string	Yes	Markdown content to import into the newly created document as blocks.
item_id	number	No	Required when location="item": item ID to attach the new document to.
doc_kind	string ("private", "public", or "share")	No	Document kind; use only when location="workspace". Defaults to public.
column_id	string	No	Optional when location="item": ID of an existing doc column. If not provided, a new doc column is created automatically.
folder_id	number	No	Optional when location="workspace": folder ID to place the document inside.
workspace_id	number	No	Required when location="workspace": workspace ID under which to create the document.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create folder

MONDAY_MCP_CREATE_FOLDER

Create a new folder in a monday.com workspace.

Input parameters

Name	Type	Required	Description
name	string	Yes	The name of the folder to be created.
workspaceId	string	Yes	The ID of the workspace where the folder will be created.
color	string	No	The color of the folder (e.g., "BRIGHT_BLUE", "PURPLE", "DONE_GREEN").
customIcon	string	No	The custom icon of the folder ("FOLDER", "WORK", etc.).
fontWeight	string	No	The font weight of the folder name ("FONT_WEIGHT_BOLD", "FONT_WEIGHT_NORMAL", etc.).
parentFolderId	string	No	The ID of the parent folder.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create form

MONDAY_MCP_CREATE_FORM

Create a monday.com form. This also creates a new board to store form responses. The returned board_id is the ID of that board; the formToken is used for all future form operations.

Input parameters

Name	Type	Required	Description
destination_workspace_id	string	Yes	The workspace in which the form will be created.
board_kind	string ("private", "public", or "share")	No	The board kind for the response board.
board_owner_ids	array	No	Array of user IDs who will have owner permissions on the response board.
destination_name	string	No	The name of the board created to store form responses.
board_owner_team_ids	array	No	Array of team IDs whose members will have owner permissions on the board.
board_subscriber_ids	array	No	Array of user IDs who will receive board activity notifications.
destination_folder_id	string	No	The folder in which the form will be created.
destination_folder_name	string	No	The name of the folder in which the form will be created.
board_subscriber_teams_ids	array	No	Array of team IDs whose members will receive board activity notifications.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create group

MONDAY_MCP_CREATE_GROUP

Create a new group in a monday.com board. Groups are sections that organize related items. They can be positioned relative to existing groups and assigned predefined colors.

Input parameters

Name	Type	Required	Description
boardId	string	Yes	The ID of the board to create the group in.
groupName	string	Yes	The name of the new group (maximum 255 characters).
groupColor	string	No	The color for the group. Must be one of the predefined monday.com group colors (e.g., "#00c875", "#579bfc", "#df2f4a").
relativeTo	string	No	The ID of the group to position the new group relative to.
positionRelativeMethod	string ("after_at" or "before_at")	No	Whether to position the new group before or after the reference group.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create item

MONDAY_MCP_CREATE_ITEM

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 for subitems and duplicateFromItemId for copying with modifications.

Input parameters

Name	Type	Required	Description
name	string	Yes	The name of the new item to be created.
boardId	number	Yes	The ID of the board to which the new item will be added.
columnValues	string	Yes	String with column values in format {"column_id": "value", ...}. For status use {"label": "Done"}; for date use {"date": "2023-05-25"}.
groupId	string	No	The ID of the group to which the new item will be added. If not specified, it goes to the top group.
parentItemId	number	No	The ID of the parent item under which a subitem will be created.
duplicateFromItemId	number	No	The ID of the existing item to duplicate (only provide when duplicating).

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create update

MONDAY_MCP_CREATE_UPDATE

Create a new update (comment/post) on a monday.com item. Updates can include comments, notes, or discussions. You can optionally mention users, teams, or boards.

Input parameters

Name	Type	Required	Description
body	string	Yes	The update text to be created. Do not use @ to mention users — use mentionsList instead.
itemId	number	Yes	The ID of the item to which the update will be added.
mentionsList	string	No	Optional JSON array of mentions in format: [{"id": "123", "type": "User"}, {"id": "456", "type": "Team"}]. Valid types: User, Team, Board, Project.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create widget

MONDAY_MCP_CREATE_WIDGET

Create a new widget in a dashboard or board view with specific configuration settings. Always use all_widgets_schema to fetch widget schemas before creating widgets.

Input parameters

Name	Type	Required	Description
widget_kind	string ("BATTERY", "CALENDAR", "CHART", "GANTT", "NUMBER", or "TABLE")	Yes	Type of widget to create.
widget_name	string	Yes	Widget display name (1–255 UTF-8 chars).
parent_container_id	string	Yes	ID of the parent container (dashboard ID or board view ID).
parent_container_type	string ("BOARD_VIEW" or "DASHBOARD")	Yes	Type of parent container.
settings	object	No	Widget-specific settings as a JSON object conforming to the widget schema.
settingsStringified	string	No	ONLY FOR MICROSOFT COPILOT: settings as a stringified JSON of the settings field.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Create workspace

MONDAY_MCP_CREATE_WORKSPACE

Create a new workspace in monday.com.

Input parameters

Name	Type	Required	Description
name	string	Yes	The name of the new workspace to be created.
workspaceKind	string ("closed", "open", or "template")	Yes	The kind of workspace to create.
description	string	No	The description of the new workspace.
accountProductId	string	No	The account product ID associated with the workspace.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Form questions editor

MONDAY_MCP_FORM_QUESTIONS_EDITOR

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

Input parameters

Name	Type	Required	Description
action	string ("delete", "update", or "create")	Yes	The operation to perform. questionId is required when updating or deleting. The question object is required when creating or updating.
formToken	string	Yes	The unique identifier token for the form.
question	object	No	The question object for creation or update. title is required when creating.
questionId	string	No	The unique identifier for the question. Required when updating or deleting.
questionStringified	string	No	ONLY FOR MICROSOFT COPILOT: the question object as a stringified JSON.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get board activity

MONDAY_MCP_GET_BOARD_ACTIVITY

Get board activity logs for a specified time range (defaults to last 30 days).

Input parameters

Name	Type	Required	Description
boardId	number	Yes	The ID of the board to get activity for.
toDate	string	No	End date for the activity range (ISO8601DateTime format). Defaults to now.
fromDate	string	No	Start date for the activity range (ISO8601DateTime format). Defaults to 30 days ago.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get board info

MONDAY_MCP_GET_BOARD_INFO

Get comprehensive board information including metadata, structure, owners, and configuration.

Input parameters

Name	Type	Required	Description
boardId	number	Yes	The ID of the board to get information for.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get board items page

MONDAY_MCP_GET_BOARD_ITEMS_PAGE

Get all items from a monday.com board with pagination support and optional column values. Use the nextCursor from the response to get the next page when has_more is true.

Input parameters

Name	Type	Required	Description
boardId	number	Yes	The ID of the board to get items from.
limit	number	No	The number of items to get per page.
cursor	string	No	The cursor to get the next page, from the nextCursor field of the previous response.
filters	array	No	Filter configuration to apply on items. Check get_board_info for filtering guidelines.
itemIds	array	No	IDs of specific items to get. Count should be less than 100.
orderBy	array	No	Columns to order the results by.
columnIds	array	No	IDs of item columns to include in the response. Works only when includeColumns is true.
searchTerm	string	No	Search term for vague or approximate queries. Prefer structured filters for exact values.
subItemLimit	number	No	Number of sub items per item. Used only when includeSubItems is true.
includeColumns	boolean	No	Whether to include column values in the response. Omit for performance when you only need IDs/names.
filtersOperator	string ("and" or "or")	No	Logical operator for the filters.
includeSubItems	boolean	No	Whether to include sub items in the response.
filtersStringified	string	No	ONLY FOR MICROSOFT COPILOT: filters as a stringified JSON array.
orderByStringified	string	No	ONLY FOR MICROSOFT COPILOT: order by as a stringified JSON array.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get column type info

MONDAY_MCP_GET_COLUMN_TYPE_INFO

Retrieve comprehensive information about a specific column type, including JSON schema definition and metadata. Use before creating columns with create_column.

Input parameters

Name	Type	Required	Description
columnType	string	Yes	The column type to retrieve information for (e.g., "text", "status", "date", "numbers").

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get form

MONDAY_MCP_GET_FORM

Get a monday.com form by its form token. The token can be extracted from the form URL — it is the alphanumeric string between /forms/ and the ?.

Input parameters

Name	Type	Required	Description
formToken	string	Yes	The unique identifier token for the form.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get graphql schema

MONDAY_MCP_GET_GRAPHQL_SCHEMA

Fetch the monday.com GraphQL schema structure including query and mutation definitions. Filter results by operation type (read/write) to focus on queries or mutations.

Input parameters

Name	Type	Required	Description
operationType	string ("read" or "write")	No	Type of operation: "read" for queries, "write" for mutations.
random_string	string	No	Dummy parameter for no-parameter tools.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get monday dev sprints boards

MONDAY_MCP_GET_MONDAY_DEV_SPRINTS_BOARDS

Discover monday-dev sprints boards and their associated tasks boards in your account. Returns pairs of sprints boards and tasks boards with IDs, names, and workspace information.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get sprints metadata

MONDAY_MCP_GET_SPRINTS_METADATA

Get comprehensive sprint metadata from a monday-dev sprints board: ID, name, planned/actual dates, completion status, activation status, and summary document object ID.

Input parameters

Name	Type	Required	Description
sprintsBoardId	number	Yes	The ID of the monday-dev board containing the sprints.
limit	number	No	The number of sprints to retrieve (default: 25, max: 100).

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get sprint summary

MONDAY_MCP_GET_SPRINT_SUMMARY

Get the complete summary and analysis of a completed sprint: scope management, individual velocity, task distribution by type, and AI recommendations.

Input parameters

Name	Type	Required	Description
sprintId	number	Yes	The ID of the sprint to get the summary for (e.g., 9123456789). The sprint must be completed and created after 2025-01-01.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get type details

MONDAY_MCP_GET_TYPE_DETAILS

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

Input parameters

Name	Type	Required	Description
typeName	string	Yes	The name of the GraphQL type to get details for.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Get user context

MONDAY_MCP_GET_USER_CONTEXT

Fetch current user information and their relevant items (boards, folders, workspaces, dashboards). Use at the beginning of conversations to get context about who the current user is and discover their most accessed items.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

List users and teams

MONDAY_MCP_LIST_USERS_AND_TEAMS

Fetch users and/or teams data. Prioritize specific parameters in order: getMe → userIds → name (users only) → teamIds + teamsOnly. Avoid broad queries with no parameters.

Input parameters

Name	Type	Required	Description
name	string	No	Name-based user search only, with fuzzy matching. Cannot be combined with other parameters. Does not search teams.
getMe	boolean	No	Use when requesting current user information. Conflicts with all other parameters.
teamIds	array	No	Specific team IDs to fetch.
userIds	array	No	Specific user IDs to fetch.
teamsOnly	boolean	No	Fetch only teams, no users returned.
includeTeams	boolean	No	Fetches all teams in the account. Avoid — use userIds to get a specific user’s teams instead.
includeTeamMembers	boolean	No	Set to true only when you need additional member details for teams beyond names and IDs.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

List workspaces

MONDAY_MCP_LIST_WORKSPACES

List all workspaces available to the user. Returns up to 500 workspaces with their ID, name, and description.

Input parameters

Name	Type	Required	Description
page	number	No	The page number to return. Default is 1.
limit	number	No	The number of workspaces to return. Default and maximum is 100.
searchTerm	string	No	Search term to filter workspaces. Only alphanumeric characters are supported.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Move object

MONDAY_MCP_MOVE_OBJECT

Move a folder, board, or overview in monday.com. Use position for relative placement, parentFolderId for folder changes, and workspaceId for workspace moves.

Input parameters

Name	Type	Required	Description
id	string	Yes	The ID of the object to move.
objectType	string ("Board", "Folder", or "Overview")	Yes	The type of object to move.
workspaceId	string	No	The ID of the destination workspace (required when moving to a different workspace).
parentFolderId	string	No	The ID of the new parent folder (required when moving to a different folder).
accountProductId	string	No	The ID of the destination account product.
position_is_after	boolean	No	Whether to position the object after the reference object.
position_object_id	string	No	The ID of the reference object for relative positioning.
position_object_type	string ("Board", "Folder", or "Overview")	No	The type of the reference object for positioning.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Read docs

MONDAY_MCP_READ_DOCS

Get a collection of monday.com documents with their content as markdown, with pagination support and filters by ID type.

Input parameters

Name	Type	Required	Description
ids	array	Yes	Array of ID values for this query type (at least 1 required).
type	string ("ids", "object_ids", or "workspace_ids")	Yes	Query type: by document IDs, object IDs, or workspace IDs.
page	number	No	The page number to return (starts at 1). Check has_more_pages in the response.
limit	number	No	Number of docs per page (default: 25).
order_by	string ("created_at" or "used_at")	No	Order in which to retrieve docs.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Search

MONDAY_MCP_SEARCH

Search within the monday.com platform for boards, documents, forms, or folders. For users and teams use list_users_and_teams; for workspaces use list_workspaces; for items use get_board_items_page. IDs returned have a type prefix (e.g., doc-123) — remove the prefix when passing them to other tools.

Input parameters

Name	Type	Required	Description
searchType	string ("BOARD", "DOCUMENTS", or "FOLDERS")	Yes	The type of search to perform.
page	number	No	The page number to get. Default: 1.
limit	number	No	The number of items to get. Max and default: 100.
searchTerm	string	No	The search term to use.
workspaceIds	array	No	IDs of workspaces to search in. Only pass if the user explicitly asked to search within specific workspaces.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Update folder

MONDAY_MCP_UPDATE_FOLDER

Update an existing folder in monday.com.

Input parameters

Name	Type	Required	Description
folderId	string	Yes	The ID of the folder to update.
name	string	No	The new name of the folder.
color	string	No	The new color of the folder.
customIcon	string	No	The new custom icon of the folder.
fontWeight	string	No	The new font weight of the folder name.
workspaceId	string	No	The ID of the workspace containing the folder.
parentFolderId	string	No	The ID of the new parent folder.
accountProductId	string	No	The account product ID associated with the folder.
position_is_after	boolean	No	Whether to position the folder after the reference object.
position_object_id	string	No	The ID of the reference object for relative positioning.
position_object_type	string ("Board", "Folder", or "Overview")	No	The type of the reference object for positioning.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Update form

MONDAY_MCP_UPDATE_FORM

Update a monday.com form. Each call performs one action at a time: update features, appearance, accessibility, title, description, question order, tags, password, or URL.

Input parameters

Name	Type	Required	Description
action	string	Yes	The update action: activate, deactivate, shortenFormUrl, setFormPassword, createTag, deleteTag, updateTag, updateAppearance, updateAccessibility, updateFeatures, updateQuestionOrder, or updateFormHeader.
formToken	string	Yes	The unique identifier token for the form.
tag	object	No	Tag data to create, update, or delete.
form	object	No	Form data to update (appearance, accessibility, features, question order, or header).
formPassword	string	No	Password to protect the form. Required for setFormPassword.
tagStringified	string	No	ONLY FOR MICROSOFT COPILOT: tag object as a stringified JSON.
formStringified	string	No	ONLY FOR MICROSOFT COPILOT: form object as a stringified JSON.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Update workspace

MONDAY_MCP_UPDATE_WORKSPACE

Update an existing workspace in monday.com.

Input parameters

Name	Type	Required	Description
id	string	Yes	The ID of the workspace to update.
attributeKind	string ("closed", "open", or "template")	No	The new kind of the workspace.
attributeName	string	No	The new name of the workspace.
attributeDescription	string	No	The new description of the workspace.
attributeAccountProductId	number	No	The target account product ID to move the workspace to.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.

Workspace info

MONDAY_MCP_WORKSPACE_INFO

Returns the boards, docs, and folders in a workspace and which folder they are in. Returns up to 100 objects of each type.

Input parameters

Name	Type	Required	Description
workspace_id	number	Yes	The ID of the workspace to get information for.

Output

Name	Type	Required	Description
data	string	Yes	Data returned by the action execution.
error	string	No	Error message if the execution failed.
successful	boolean	Yes	Indicates whether the action was executed successfully.