Skip to main content
Back to the Campfire MCP server

MCP Gateway · Claude Cowork

Campfire icon

Connect Campfire to Claude Cowork

Month-end close is a long chain of checks, reports and write-ups. In Cowork, Claude can work through that chain against Campfire's accounting, financial report and ERP data as one task, through the Speakeasy MCP Gateway. Because financial data is sensitive, it helps that PII redaction runs on every Campfire tool call and each call is logged against a named employee.

Category
Productivity
Authentication
API key
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Campfire server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Campfire from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Campfire

Prepare a month-end close pack

Cowork gathers the financial reports and accounting data the close needs from Campfire and assembles them into one pack for review.

Reconcile figures across reports

Have Cowork compare the totals in several Campfire financial reports and list every place where they don't agree, with the data behind each gap.

Write the monthly finance summary

Cowork reads the month's Campfire reports and ERP data, then drafts the written summary that goes to leadership with the numbers.

Control

What Speakeasy can see and stop in Claude Cowork

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can personal Claude accounts reach Campfire in Cowork?
Personal Claude accounts can't be governed in Cowork, and neither the device agent nor MDM reaches Cowork, so the Claude-side plugin setup always applies.
Can prompts touching Campfire be checked before inference?
On Claude Enterprise, prompts can be checked before inference (beta). Agent hooks also send each prompt to Speakeasy before the step runs.
How do Claude Cowork users get Campfire?
An admin adds Campfire from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Campfire tools their access allows.
Are Campfire calls from Claude Cowork 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.