Skip to main content
Back to the Campfire MCP server

MCP Gateway · Codex

Campfire icon

Connect Campfire to Codex

Changes to finance code deserve a reviewer who can see the books. With Campfire behind the Speakeasy MCP Gateway, Codex can reach accounting, financial report and ERP data while it reviews or writes that code. Prompt injection detection and PII redaction run on every Campfire tool call, and each call lands in an audit log tied to a named employee.

Category
Productivity
Authentication
API key
Codex
CLI and ChatGPT desktop app

Behind the MCP Gateway

Run Campfire MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Campfire call inspected and logged.

Deploy on MCP Gateway

Set up

Add Campfire to Codex in 4 steps

  1. 01

    Add Campfire from the catalog

    An admin finds Campfire 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.

    Campfire authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.

    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.

  2. 02

    Choose who can use Campfire

    Give teams the mcp:connect scope on the Campfire server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Campfire to their gateway on the next call, and removing it takes it away.

  3. 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'
  4. 04

    Sign in and use Campfire from Codex

    The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Campfire'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 Campfire

Review a change against the books

While reviewing a pull request that touches financial logic, Codex reads the related Campfire accounting data and checks whether the change agrees with it.

Explain a report difference

When a nightly job's totals drift from Campfire's financial report, ask Codex to fetch the report and pin down which entries account for the gap.

Write an ERP mapping from real data

Codex reads ERP data from Campfire before drafting a mapping between Campfire and an internal system, so field names come from the source.

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 Campfire call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Campfire tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Campfire 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 Codex hold a Campfire credential?
No. Agents never hold a Campfire credential, and access ends when the employee leaves the directory.
Are Campfire calls from Codex cloud tasks covered?
Codex cloud tasks and GitHub code review run off the device, so neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
How do Codex users get Campfire?
An admin adds Campfire from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Campfire tools their access allows.
Are Campfire calls from Codex logged?
Yes. Campfire calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Campfire in other clients

AI everywhere.

Control here.