Skip to main content
Back to the Monday.com MCP server

MCP Gateway · Claude Cowork

Monday.com icon

Connect Monday.com to Claude Cowork

Setting up a new monday.com project often takes an afternoon of boards, columns, dashboards and folders. Give Cowork a short brief and it works through that setup as one longer task while you do something else. Admins make monday.com available by syncing Speakeasy's plugin repository into Claude, and every prompt is allowed or denied by Speakeasy before the step goes ahead.

Category
Project management
Tools
41
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Monday.com MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Monday.com call inspected and logged.

Deploy on MCP Gateway

Set up

Add Monday.com to Claude Cowork in 4 steps

  1. 01

    Add Monday.com from the catalog

    An admin finds Monday.com in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Monday.com uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Monday.com

    Give teams the mcp:connect scope on the Monday.com server through team access or a role. Claude Cowork connects to the Monday.com server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Monday.com from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Monday.com needs its own OAuth grant, so each person connects it once. Until they do, Monday.com calls fail while the rest of the gateway keeps working.

    From then on, Monday.com's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Monday.com

Build a project board from a brief

Cowork creates the board, adds a group for each phase of your brief, and creates the columns the team will track, such as owner, status and due date.

create_boardcreate_groupcreate_column

Create a dashboard for leadership

Cowork creates a dashboard that pulls from the project boards, checks the widget schemas, and adds widgets for the figures leadership asks about.

create_dashboardall_widgets_schemacreate_widget

Reorganize a cluttered workspace

Cowork lists the workspace's boards, docs and folders, creates folders by team or quarter, and moves each board into place.

workspace_infocreate_foldermove_object

Tools

41 tools

Each Monday.com tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.

get_board_items_page

com board with pagination support and optional column values and item descriptions. Returns structured JSON with item details, creation/update timestamps, and pagination info.

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 when creating a subitem under an existing item. ), first use get_board_info to understand the board metadata.

create_update

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.

get_updates

com item or board. Specify objectId and objectType (Item or Board) to retrieve updates. For Board queries, you can filter by date range using fromDate and toDate (both required together, ISO8601 format).

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. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object.

See all 41 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Monday.com call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Monday.com tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Monday.com can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

How do plugin changes for monday.com reach Cowork?
Cowork reads the synced plugin repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Can prompts in Cowork be checked before inference?
On Claude Enterprise, Anthropic inference hooks can check prompts before inference (beta). Speakeasy's agent hooks also allow or deny each prompt before the step runs.
How do Claude Cowork users get Monday.com?
An admin adds Monday.com from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Monday.com tools their access allows.
Are Monday.com calls from Claude Cowork logged?
Yes. Monday.com calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Monday.com in other clients

AI everywhere.

Control here.