Skip to main content
Back to the Campfire MCP server

MCP Gateway · Claude Code

Campfire icon

Connect Campfire to Claude Code

Finance systems engineers build integrations that sit on top of the books. With Campfire behind the Speakeasy MCP Gateway, Claude Code can reach accounting, financial report and ERP data from the terminal while you work on that code. Claude Code's OpenTelemetry exporter ties each session to a named person, so every look at financial data has an owner.

Category
Productivity
Authentication
API key
Claude Code
CLI

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 Claude Code 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 Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Campfire from Claude Code

    The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Campfire

Check accounting data while coding

When you build an integration that reads from the ledger, ask Claude Code to pull the matching accounting records from Campfire so your code handles real shapes of data.

Compare a report with a pipeline

If a revenue pipeline's output looks off, have Claude Code fetch the corresponding Campfire financial report and compare the totals with what your job produced.

Look up ERP data for a fix

While fixing a sync between Campfire and another system, Claude Code reads the ERP data involved instead of you copying values out of a browser.

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can I limit which Campfire tools Claude Code can call?
Yes. You decide which Campfire tools each team can call at the gateway, so engineering, support and finance each get only the access their role needs.
Can Claude Code's spending be capped while it works with Campfire?
Spend limits can block Claude Code traffic once a budget is reached.
How do Claude Code users get Campfire?
An admin adds Campfire from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Campfire tools their access allows.
Are Campfire calls from Claude Code 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.