MCP Gateway · OpenCode
Connect Monday.com to OpenCode
OpenCode users can check monday.com from the same terminal they ship from. The agent lists the boards and items assigned to you, reviews what changed on a board after a release, and adds a group to organize the follow-up. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
- Category
- Project management
- Tools
- 41
- Authentication
- OAuth
- OpenCode
- Terminal
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.
Set up
Add Monday.com to OpenCode in 4 steps
- 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.
- 02
Choose who can use Monday.com
Give teams the
mcp:connectscope on the Monday.com server through team access or a role. OpenCode connects to the Monday.com server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Monday.com from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Monday.com
See what is assigned to you
At the start of a session, OpenCode fetches your user context, including the boards, folders and items relevant to you, and suggests which item to pick up.
Review board activity after a release
After a deploy, OpenCode reads the board's activity log for the last few days to confirm items were moved and to catch any that were missed.
Group follow-up work for a release
OpenCode creates a new group on the board for the release's follow-up work and adds an item for each loose end it found in the code.
Tools
41 tools
Each Monday.com tool can be allowed or denied per team and role at the MCP Gateway before OpenCode 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.
Control
What Speakeasy can see and stop in OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Does OpenCode receive monday.com from a Speakeasy plugin?
How is tool output from monday.com controlled in OpenCode?
How do OpenCode users get Monday.com?
Are Monday.com calls from OpenCode logged?
Connect more