Skip to main content
Back to the Campfire MCP server

MCP Gateway · Cursor

Campfire icon

Connect Campfire to Cursor

Developers who maintain finance tooling need the numbers next to the code that produces them. Through the Speakeasy MCP Gateway, the Cursor agent can reach Campfire's accounting, financial report and ERP data while you edit, so test fixtures and checks reflect the real books. Every Cursor hook event carries the user's email, so access to financial data is attributed.

Category
Productivity
Authentication
API key
Cursor
Editor and 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.

Deploy on MCP Gateway

Set up

Add Campfire to Cursor 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 Cursor

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Campfire from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Campfire

Base fixtures on real ledger data

Ask Cursor to read the accounting entries a feature depends on from Campfire, then write test fixtures in the editor that match their structure.

Validate a reporting change

Before merging a change to report generation, Cursor pulls the existing Campfire financial report so you can check your output against it line by line.

Trace an ERP sync issue

With the sync code open, have Cursor fetch the ERP records that failed to match and reason about where your mapping goes wrong.

Control

What Speakeasy can see and stop in Cursor

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

What happens if Speakeasy can't check a Campfire call in Cursor?
Cursor hooks fail closed. If Speakeasy can't allow a prompt or tool call, Cursor doesn't run it.
Why don't Campfire tools show on this page?
The registry hasn't published an individual tool list for the Campfire server yet. The server reaches accounting, financial report and ERP data.
How do Cursor users get Campfire?
An admin adds Campfire from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Campfire tools their access allows.
Are Campfire calls from Cursor 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.