MCP Gateway · Codex
Connect ClickUp to Codex
For engineering teams using Codex, ClickUp holds the backlog, sprint statuses and links between tasks. Through the Speakeasy MCP Gateway, Codex can file tasks during review, link related work and report how long tasks sit in each status. Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
- Category
- Project management
- Tools
- 51
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run ClickUp MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every ClickUp call inspected and logged.
Set up
Add ClickUp to Codex in 4 steps
- 01
Add ClickUp from the catalog
An admin finds ClickUp 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.
ClickUp 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 ClickUp
Give teams the
mcp:connectscope on the ClickUp server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds ClickUp 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 ClickUp from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
ClickUp needs its own OAuth grant, so each person connects it once. Until they do, ClickUp calls fail while the rest of the gateway keeps working.
From then on, ClickUp'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 ClickUp
Turn a review comment into a task
When code review raises something out of scope, Codex asks which list to use, looks up its ID and creates a ClickUp task with the file and the reviewer's point.
Link frontend and backend tasks
When a change spans two repositories, Codex links the matching ClickUp tasks so each team can see the other half of the work.
See where sprint work stalled
Codex pulls status history for up to 100 tasks at once and shows how long each spent in review, ready for the sprint retro.
Tools
51 tools
Each ClickUp tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
clickup_search
Universal search across your entire ClickUp workspace. This is a powerful global search tool that finds ANY type of content - tasks, documents, dashboards, attachments, whiteboards, chat messages, and forms.
clickup_get_workspace_hierarchy
Get workspace hierarchy (spaces, folders, lists) from your authenticated workspace with pagination support. Workspace ID is automatically detected from your session. Returns tree structure with names and IDs for navigation.
clickup_create_task
Create task in a ClickUp list. Requires task name and list_id. ALWAYS ask user which list to use - never guess. Use clickup_get_list to resolve list names to IDs. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature').
clickup_get_task
Get task details by task_id (works with regular/custom IDs). Set subtasks=true to include all subtask details.
clickup_filter_tasks
Retrieve tasks with combined filters. Supports filtering by tags, lists, folders, spaces, statuses, assignees, due date range, and completion date range. , tags: ["bug", "feature"] returns tasks with either tag).
clickup_update_task
Update task properties. Requires task_id and at least one update field. Custom fields supported as array of {id, value}. Supports assignees as array of user IDs, emails, usernames, or "me". , 'Bug', 'Feature'), or null to reset to default.
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 ClickUp call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the ClickUp tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to ClickUp 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
How are ClickUp calls from Codex tied to a person?
Why don't team members see ClickUp in Codex after the import?
How do Codex users get ClickUp?
Are ClickUp calls from Codex logged?
Connect more