MCP Gateway · Codex
Connect Slack to Codex
Codex can search Slack for the context behind a change and prepare the message that goes out with it. Engineers reach Slack through the Speakeasy MCP Gateway with one URL, each person authorizes with their own Slack account, and an admin sets which Slack tools each team can call.
- Category
- Communication
- Tools
- 13
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Slack MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Slack call inspected and logged.
Before you start
What Slack needs first
A user who can create or manage a Slack app, plus any required workspace-admin approval does the Slack side of the setup.
- You need permission to create or manage the app and any required workspace-admin approval.
- Only internal apps and Slack Marketplace apps can use the MCP server.
- Each user authorizes with their own Slack account. No bot token or API key is used.
In Slack
- Create the app from Speakeasy's prefilled manifest link, or enable MCP on an existing app.
- Remove any user scopes you do not want to grant.
- Copy the app's client credentials.
Set up
Add Slack to Codex in 4 steps
- 01
Add Slack from the catalog
An admin finds Slack 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.
Slack 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 Slack
Give teams the
mcp:connectscope on the Slack server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Slack 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 Slack from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Slack needs its own OAuth grant, so each person connects it once. Until they do, Slack calls fail while the rest of the gateway keeps working.
From then on, Slack'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 Slack
Search earlier reports of an error
Give Codex an error string from the logs and it searches public channels for earlier mentions, so you can see whether someone hit the same failure before and what they tried.
Schedule a maintenance notice
Before a planned database change, Codex writes the notice and queues it for delivery at the start of the maintenance window rather than posting it right away.
Stage release notes as a draft
Codex turns a commit range into a release summary and saves it as a Slack draft in the release channel, so you can review the wording in Slack before sending it yourself.
Tools
13 tools
Each Slack tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
slack_send_message
Sends a message to a Slack channel or user. To DM a user, use their user_id as channel_id. Return the message link to the user.
slack_schedule_message
Schedules a message for future delivery to a Slack channel. Does NOT send immediately — use slack_send_message for that.
slack_create_canvas
Creates a Slack Canvas document from Canvas-flavored Markdown content. Return the canvas link to the user. Not available on free teams.
slack_update_canvas
Updates an existing Slack Canvas document with markdown content. Supports appending, prepending, or replacing content.
slack_search_public
Searches for messages, files in public Slack channels ONLY.
slack_search_public_and_private
Searches for messages, files in ALL Slack channels, including public channels, private channels, DMs, and group DMs.
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 Slack call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Slack tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Slack 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 the Slack setup cover Codex cloud tasks?
Which Slack apps can expose the MCP server to Codex?
How do Codex users get Slack?
Are Slack calls from Codex logged?
Connect more