MCP Gateway · Codex
Connect Linear to Codex
Codex often works through larger changes than one sitting allows. With Linear available through the Speakeasy MCP Gateway, it can split that work into tracked issues, attach what it produced, and check the cycle a fix belongs to. Agent hooks send each prompt and Linear tool call to Speakeasy before Codex runs it.
- Category
- Project management
- Tools
- 31
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Linear MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Linear call inspected and logged.
Set up
Add Linear to Codex in 4 steps
- 01
Add Linear from the catalog
An admin finds Linear 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.
Linear 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 Linear
Give teams the
mcp:connectscope on the Linear server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Linear 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 Linear from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Linear needs its own OAuth grant, so each person connects it once. Until they do, Linear calls fail while the rest of the gateway keeps working.
From then on, Linear'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 Linear
Split a large change into issues
When a refactor is too big for one pull request, ask Codex to plan it and file each step as its own issue in the project, in the order they need to land.
Attach test output to an issue
After reproducing a bug from the terminal, Codex uploads the failing test log to the Linear issue so reviewers see the evidence without rerunning anything.
Check which cycle a fix lands in
Before you pick up a fix, Codex lists the team's cycles and the issue's current status so you know whether it is due this week or can wait.
Tools
31 tools
Each Linear tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
get_attachment
Retrieve an attachment's content by ID.
create_attachment
Create a new attachment on a specific Linear issue by uploading base64-encoded content.
delete_attachment
Delete an attachment by ID
list_comments
List comments for a specific Linear issue
save_comment
Create or update a comment on a Linear issue. If id is provided, updates the existing comment; otherwise creates a new one. When creating, issueId and body are required.
delete_comment
Delete a comment from a Linear issue
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 Linear call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Linear tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Linear 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 cover Codex cloud tasks that use Linear?
How is Linear activity in Codex tied to a person?
How do Codex users get Linear?
Are Linear calls from Codex logged?
Connect more