MCP Gateway · OpenCode
Connect Campfire to OpenCode
Month-end scripts and finance data jobs often run from a terminal. From OpenCode, through the Speakeasy MCP Gateway, you can reach Campfire's accounting, financial report and ERP data while you write and debug those scripts. The OpenCode plugin checks each prompt and tool call with Speakeasy and reports token and cost totals per turn.
- Category
- Productivity
- Authentication
- API key
- OpenCode
- Terminal
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.
Set up
Add Campfire to OpenCode in 4 steps
- 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.
- 02
Choose who can use Campfire
Give teams the
mcp:connectscope on the Campfire server through team access or a role. OpenCode connects to the Campfire server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Campfire from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Campfire
Debug a month-end script
When a close script fails on an account, ask OpenCode to pull the Campfire accounting data for that account and see what the script didn't expect.
Spot-check a financial report
After an export job runs, have OpenCode read the same financial report from Campfire and confirm the headline figures match the exported file.
Inspect ERP records from the shell
Read the ERP data a data job depends on straight from the terminal, without opening Campfire's UI while you work through a fix.
Control
What Speakeasy can see and stop in OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Is Campfire tool output filtered in OpenCode?
Can the device agent maintain OpenCode's Speakeasy setup?
How do OpenCode users get Campfire?
Are Campfire calls from OpenCode logged?
Connect more