Monday MCP

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.

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.

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.

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

Create a monday.com board

Create a new column in a monday.com board

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

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) - 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: "..." }

Create a new folder in a monday.com workspace

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

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

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.

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 a new workspace in monday.com

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

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

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

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

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

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 token is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the token is abc123def456ghi789.

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.

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.

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.

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.

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

Fetch current user information and their relevant items (boards, folders, workspaces, dashboards). Use this tool at the beginning of conversations to: - Get context about who the current user is (id, name, title) - Discover user's favorite boards, folders, workspaces, and dashboards - Get user's most relevant boards based on visit frequency and recency - Reduce the need for search requests by knowing user's commonly accessed items

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.

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

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.

Get a collection of monday.com documents with their content as markdown. PAGINATION: - Default limit is 25 documents per page - Use 'page' parameter to get additional pages (starts at 1) - Check response for 'has_more_pages' to know if you should continue paginating - If user asks for "all documents" and you get exactly 25 results, continue with page 2, 3, etc. FILTERING: Provide a type value and array of ids: - type: 'ids' for specific document IDs - type: 'object_ids' for specific document object IDs - type: 'workspace_ids' for all docs in specific workspaces - ids: array of ID strings (at least 1 required) Examples: - { type: 'ids', ids: ['123', '456'] } - { type: 'object_ids', ids: ['123'] } - { type: 'workspace_ids', ids: ['ws_101'] } USAGE PATTERNS: - For specific documents: use type 'ids' or 'object_ids' (A monday doc has two unique identifiers) - For workspace exploration: use type 'workspace_ids' with pagination - For large searches: start with page 1, then paginate if has_more_pages=true

Search within monday.com platform. Can search for boards, documents, forms, folders. For users and teams, use list_users_and_teams tool. For workspaces, use list_workspaces tool. For items and groups, use get_board_items_page tool. For groups, use get_board_info tool. IMPORTANT: ids returned by this tool are prefixed with the type of the object (e.g doc-123, board-456, folder-789). When passing the ids to other tools, you need to remove the prefix and just pass the number.

Update an existing folder in monday.com

Update a monday.com form. Handles the following form update actions that can only be done one at a time using the correct "action" input: - update form's feature settings with the action "updateFeatures", - update form's appearance settings with the action "updateAppearance", - update form's accessibility settings with the action "updateAccessibility", - update form's title with the action "updateFormHeader", - update form's description with the action "updateFormHeader", - update form's question order with the action "updateQuestionOrder", - create a new form tag with the action "createTag", - delete a form tag with the action "deleteTag", - update a form tag with the action "updateTag", - set or update the form's password with the action "setFormPassword" - shorten form's url with the action "shortenFormUrl" - deactivate form with the action "deactivateForm" - reactivate form with the action "activateForm"

Update an existing workspace in monday.com

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.