mondaycom/mcp

delete_item

Delete an item

get_board_items_by_name

Get items by board id and term

create_item

Create a new item in a monday.com board

create_update

Create a new update in a monday.com board

get_board_schema

Get board schema (columns and groups) by board id

get_board_activity

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

get_board_info

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

get_users_by_name

Get users, can be filtered by name or partial name

list_users_and_teams

PRECISION-FIRST user and team retrieval tool. AI agents MUST prioritize specific queries over broad searches.

  MANDATORY BEST PRACTICES:
  1. ALWAYS use specific IDs when available (userIds, teamIds) - highest precision and performance
  2. ALWAYS use name search when you have user names but no IDs  
  3. ALWAYS use boolean getMe: true when requesting current user information
  4. AVOID broad queries (no parameters) - use only as absolute last resort
  5. COMBINE parameters strategically to minimize API calls

  REQUIRED PARAMETER PRIORITY (use in this order):
  1. getMe: true (when requesting current user) - STANDALONE ONLY
  2. name="exact_name" (when searching by name) - STANDALONE ONLY  
  3. userIds=["id1","id2"] (when you have specific user IDs)
  4. teamIds=["id1","id2"] + teamsOnly: true (when you have specific team IDs)
  5. No parameters (LAST RESORT - fetches up to 1000 users, avoid unless absolutely necessary)

  CRITICAL USAGE RULES:
  • getMe and name parameters CANNOT be combined with any other parameters
  • userIds + teamIds requires explicit includeTeams: true flag
  • teamsOnly: true prevents user data fetching (teams-only queries)
  • includeTeamMembers: true adds detailed member data to teams
  • includeTeams: true fetches both users and teams, can be used to get a user's teams if their user id is known

  OPTIMIZATION DIRECTIVES:
  • NEVER fetch all users when specific IDs are available
  • NEVER use broad queries for single user/team lookups  
  • ALWAYS prefer name search over ID-less queries for individual users
  • SET includeTeamMembers: false for team lists, true only for member analysis  
  • AVOID includeTeams: true unless you specifically need both users AND teams
  • AVOID broad queries for single user/team, if you have specific IDs, use them. For example getting a user's teams, use that user's ID and fetch their team using the includeTeams flag.

  RESPONSE CONTENT:
  • Users: id, name, email, title, permissions, contact details, team memberships
  • Teams: id, name, owners, members (when includeTeamMembers: true)
  • Current user: id, name, title, enabled, is_admin, is_guest (basic profile only)

change_item_column_values

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

move_item_to_group

Move an item to a group in a monday.com board

create_board

Create a monday.com board

create_form

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.

get_form

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.

create_column

Create a new column in a monday.com board

create_group

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

delete_column

Delete a column from a monday.com board

get_column_type_info

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.

create_custom_activity

Create a new custom activity in the E&A app

create_timeline_item

Create a new timeline item in the E&A app

fetch_custom_activity

Get custom activities from the E&A app

create_workflow_instructions

When the user asks to create a workflow or automation, you must use this tool, which provides instructions on how to create a workflow. This tool is very important and should be used when the user explicitly requests: - Workflow creation (e.g., "create a monday workflow", "create a new workflow"). - Automation (e.g., "automate this process", "when item is created, set status to done")

read_docs

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 an ID filter object with:

• type: 'ids' for specific document IDs
• type: 'object_ids' for specific document object IDs
• type: 'workspace_ids' for all docs in specific workspaces
• values: array of ID strings (at least 1 required)

Examples:

• { type: 'ids', values: ['123', '456'] }
• { type: 'object_ids', values: ['123'] }
• { type: 'workspace_ids', values: ['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

workspace_info

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.

list_workspaces

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

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.

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: { type: "workspace", workspace_id: 123, doc_kind: "private" }, markdown: "..." }
• Workspace doc in folder: { location: { type: "workspace", workspace_id: 123, folder_id: 17264196 }, markdown: "..." }
• Item doc: { location: { type: "item", item_id: 456, column_id: "doc_col_1" }, markdown: "..." }

create_dashboard

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

all_widgets_schema

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.

create_widget

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