Campfire MCP server and Claude connector: what it reads, what access it gets, how to connect

Campfire runs an official hosted MCP server at api.meetcampfire.com/mcp with 12 read-only tools for ledger data and reports, also listed as a Claude connector. Verified 21 Oct 2026.

Official remote MCP server · read-only
Claude connector · read-only

Hosting: Remote HTTP, hosted by Campfire (https://api.meetcampfire.com/mcp). No local or open-source server.
Auth: OAuth sign-in (the server advertises OAuth 2.0 and the Claude connector asks you to sign in) or a Campfire API key sent as an Authorization header
Read / write: Read-only: all 12 documented tools retrieve records or generate reports
Works with: Claude.ai and Claude Desktop (connector), Cursor and VS Code (per Campfire), Claude Code and other remote-capable MCP clients
Plan requirement: An active Campfire account. Campfire doesn't document a plan tier or extra fee for MCP
Last changed: February 2026 (Campfire connector added to the Claude directory)
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Campfire through MCP?

It can read your chart of accounts, general ledger transactions, company dimensions, budgets, revenue contracts and aging, and generate the three core financial statements. Campfire documents no tool that creates or changes records.

Tools

Campfire's guide lists 12 tools, each mapped to a Campfire API endpoint, in four groups. The Claude directory shows the same 12 tool names, such as get_transactions, income_statement and get_aging.

Group	Tools
Core accounting	2
Company data	4
Financial reports	3
Budgeting and revenue	3

Good to know

Transactions can be filtered by entity, account, vendor, department, tag and date range.
The income statement supports monthly, quarterly or yearly cadence.
Campfire says results are always scoped to the organisation tied to your sign-in or API key.

Can

Read the chart of accounts, filtered by type, subtype or a search term
Search general ledger transactions by entity, account, vendor, department, tag and date range
Read entities, the vendor directory, the department hierarchy and transaction tags
Generate an income statement, balance sheet and cash flow statement for a period
Read budgets, revenue recognition contracts with performance obligations, and AP/AR aging by age bucket

Cannot

Create, edit or post journal entries, bills or invoices (no write tools are documented by Campfire)
Pay bills, move cash or approve anything in Campfire (no such tools are listed)
Read data from more than one organisation per connection (results are scoped to the token's organisation, per Campfire)

What access does it get?

Read access to one Campfire organisation, either through an OAuth sign-in or through an API key. With a key, the role of the API user behind it sets what it can reach.

Where	Scopes and permissions (as documented)	Admin requirement
Claude connector and OAuth sign-in (remote)	Campfire's docs don't list the scopes the connector requests. The server's published OAuth metadata advertises campfire.mcp.read, campfire.mcp.reports.read, campfire.mcp.support.read and campfire.mcp.write, plus openid, email and profile; Campfire doesn't document what campfire.mcp.write enables.	Campfire doesn't document who can authorise the connector. Claude Team/Enterprise: an Owner adds the connector before members can connect.
API key in an Authorization header (remote)	The key carries no scopes. It belongs to an API user, and access depends on that user's role: admin (all APIs), clerk (view all APIs and post draft entries) or view only (GET APIs only). Campfire warns a key gives full access to your Campfire data.	Created under Settings > API Keys by a logged-in Campfire user; Campfire doesn't document which user roles may create API users.

How do I connect it?

The Claude connector is the quickest setup. For Cursor, VS Code or Claude Code, add the remote URL https://api.meetcampfire.com/mcp to your client.

In Claude.ai, open https://claude.com/marketplace/connectors/campfire and click Add to Claude (or use Customize > Connectors). In Claude Desktop, Campfire's documented steps are Settings > Connectors, search for Campfire and click Connect.
Sign in to Campfire when prompted.
Restart the app if the tools don't appear, then ask about your statements, transactions or aging.
Team/Enterprise: an Owner must add the connector before members can connect.

Read-only. Campfire doesn't document which Claude plans the connector needs.

What should a finance team watch for?

The main risk is the credential: Campfire says an API key gives full access to your Campfire data, so use the least-privileged role and keep keys out of shared files.

Campfire documents the API rate limit as 10 requests per second per API user, shared across endpoints, with 429 errors over the limit. It doesn't state a separate MCP limit. Campfire says large lists are paged, so a broad transaction search or a full-period ledger pull can take several calls.
One connection reaches one Campfire organisation, per Campfire; accounting firms need a separate sign-in or key per client.
Create a dedicated API user with the view only role for MCP. An admin or clerk key would carry more access than the 12 read tools need, including posting draft entries (clerk) or all APIs (admin). Campfire doesn't document which role the MCP server needs, so if a tool fails with a view-only key, check with Campfire before raising the key to clerk or admin.
Campfire says AI tools securely store your token locally, but an API key header sits in plain text in client config: Cursor's mcp.json, VS Code's workspace file .vscode/mcp.json (often committed), and Claude Code's config when added with claude mcp add (a project-scoped .mcp.json can be committed). Keep these files out of version control and out of synced or shared folders, and use the client's secret storage where it offers one.
Campfire's server advertises a campfire.mcp.write OAuth scope that its docs don't explain. Today's documented tools are read-only; re-check the tool list before relying on that.
Campfire says data is only accessed when you request it through the AI tool. Its privacy policy (updated 12 Jun 2026) says Google user data and Google Workspace data aren't used to train generalised AI models, but makes no such statement about accounting or other customer data, so check Campfire's and your AI provider's terms.
Vendor names, tags and transaction descriptions come back as free text. An injected instruction there could steer the agent to misreport figures or to act through other connected tools, so review outputs before they leave the chat.

How could finance teams and accounting firms use it?

Because every documented tool is read-only, it suits questions, reviews and reporting drafts that a person checks against Campfire.

Inside a company

Ask for the income statement by month for the quarter and the budget for the same period; the agent works out the variance itself from the two results, so tie it to Campfire's own budget-vs-actual view before using it.
Pull AP aging before a payment run and draft a short list of overdue bills for a person to review in Campfire.
Search transactions by vendor, department or tag to explain an unusual expense line.
Draft first-pass management commentary from the income statement, balance sheet and cash flow, then edit it.

At an accounting firm

Prepare for a client meeting by summarising the period's results and AR aging for that organisation.
Run month-end review questions (unusual balances, large transactions, unexpected vendors) before sign-off.
Check revenue recognition contracts and their performance obligations against what the client reports.
Review AP aging and the vendor list ahead of a client's payment run.

Whatever the use, keep a person approving any change to the ledger in Campfire itself, and treat AI-produced figures as drafts until they tie to Campfire's reports.

Want Campfire connected to Claude for your team?

We set up scoped connections, with a review step before anything changes your books, for a fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-21	Remote server advertises OAuth sign-in and four campfire.mcp scopes; Campfire's setup snippets now show the URL only	api.meetcampfire.com/.well-known/oauth-protected-resource/mc
2026-02	Campfire connector added to the Claude directory (12 tools)	claude.com/marketplace/connectors/campfire
2026	Campfire MCP server documented with 12 tools at api.meetcampfire.com/mcp	docs.campfire.ai/guides/ai-integration

FAQ

Is this official?

Yes. Campfire documents the server in its developer docs, hosts it at api.meetcampfire.com, and publishes the Claude connector, which the Claude directory marks as Anthropic verified.

Is it free?

Campfire doesn't state a price or plan requirement for MCP. You need an active Campfire account, plus a Claude or other AI client plan.

Does it change data in Campfire?

Not through the documented tools: all 12 retrieve records or generate reports. The server advertises a write scope Campfire hasn't documented, so re-check the tool list over time.

Is my data used to train models?

Campfire says data is only accessed when you request it through your AI tool, but doesn't address model training for this server. Check Campfire's terms and your AI provider's terms.

Can my accountant use it on my behalf?

Campfire doesn't document this for MCP. Access follows the sign-in or API key used, so an accountant would need their own Campfire access to your organisation or a key you issue for them.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.