MCP Gateway · Codex
Connect Monday.com to Codex
For engineering teams on monday dev, Codex can check sprint scope from the terminal, run a one-off GraphQL query when no dedicated tool fits, and notify a teammate when their part is ready. Agent hooks send each prompt and monday.com tool call to Speakeasy, which allows or denies it before Codex acts.
- Category
- Project management
- Tools
- 41
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
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 Codex 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. The organization gateway works out each person's servers from their live access, so granting access adds Monday.com to their gateway on the next call, and removing it takes it away. - 03
Connect Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Monday.com from Codex
The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Monday.com
Check sprint scope before starting
Codex finds the team's monday dev sprints board and reads the current sprint's metadata, so you know what is committed before you start a branch.
Run a one-off GraphQL query
When you need data no other tool returns, such as a field across many boards, Codex writes the GraphQL query, asks only for the fields it needs and runs it.
Tell a teammate a fix is ready
When Codex finishes the part another person is waiting on, it sends them a monday.com notification on the related item, with an optional email.
Tools
41 tools
Each Monday.com tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex
The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Does Speakeasy see Codex cloud tasks that use monday.com?
Can Codex's monday.com usage be capped?
How do Codex users get Monday.com?
Are Monday.com calls from Codex logged?
Connect more