Campfire
by Campfire
Query a Campfire accounting ledger and generate financial statements from an AI agent. 12 read-only tools over a 447-endpoint API, OAuth or API token sign-in, and a write scope no listed tool uses.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Campfire via MCP
https://api.meetcampfire.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Campfire Tools & Capabilities (12)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- A write scope exists that no listed tool uses.
campfire.mcp.writeis advertised by Campfire's authorization server and its resource descriptor, while all 12 listed tools are reads. We could not determine whether it is reserved for future tools or backs tools outside this listing. Decline it at consent unless you know why you need it. - The API-token route makes the role the boundary, not the tool list. Campfire states the MCP server calls Campfire API endpoints with your credentials, and that an API user's role decides which APIs the key reaches —
admingrants all APIs. A curated 12-tool surface does not narrow an admin key; it only narrows what the agent is offered. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-22, so no parameter-level detail or server-declared read-only hints are published here.
- Campfire publishes no tool identifiers. Its guide describes all 12 tools by label only, so the names on this page are Anthropic's. A rename would be undetectable from outside.
- The aging tool has no documented endpoint. No page in Campfire's 447-page API reference mentions aging, so its parameters and response shape cannot be checked in advance.
- Most of Campfire is out of reach. Journal entries, bills, invoices, bank reconciliation, fixed assets, files and webhooks all have documented REST endpoints and no MCP tool. Roughly 447 documented endpoints reduce to 12.
- Statement coverage is narrower than the API's. Trial balance, comparative balance sheet, comparative income statement, general ledger, custom reports and cash-basis statements are documented REST endpoints with no corresponding tool.
- Campfire publishes no MCP rate limits. Its documentation names none for the MCP server, and we did not test. Treat throughput as unknown.
- Tool output is untrusted input. Vendor names,
merchant_nameand custom-field values are free text entered by people in your organisation and by your counterparties. Treat retrieved ledger content as data, never as instructions.
Frequently asked questions
No tool in the listing can. All 12 names carry read verbs, and Campfire's own documentation describes every one as retrieving or generating. But Campfire's authorization server advertises a campfire.mcp.write scope alongside the two read scopes, so a write surface is provisioned at the OAuth layer that no listed tool consumes.
Your general ledger and the people behind it. The transactions tool returns posted amounts, vendor names and free-text merchant names, and the vendors tool returns what Campfire calls a vendor/customer directory carrying email addresses, phone numbers, and billing and shipping addresses. That is financial records plus contact personal data in one grant.
Twelve of roughly 447. Campfire's documentation index listed 447 API reference pages on 2026-08-22, covering create, update, void and delete operations across payables, receivables and journal entries. The MCP server is a deliberately curated read-only slice, not a wrapper over the whole API.
It needs a Campfire account and an API user. Campfire's quickstart states you must have an active account to mint tokens, and that the API user's role decides which APIs the key reaches — admin for all APIs, clerk for viewing plus posting draft entries, and view only for GET requests alone. Campfire publishes no separate MCP plan gate.
Six, and three of them are real boundaries. Campfire's RFC 9728 descriptor advertised campfire.mcp.read, campfire.mcp.reports.read and campfire.mcp.write on 2026-08-22, plus the openid, profile and email identity claims. Separating ledger reads from report generation is a finer split than most connectors offer.
Your token is missing, wrong or expired. Campfire's troubleshooting guidance lists three checks: verify the API token is correct, confirm it has not expired, and confirm the authorization header is configured in your MCP settings. The server's own error hint names two accepted header forms, Token for a Knox key and Bearer for an OAuth token.
No. Campfire's REST API documents outbound and money-moving operations including sending a credit memo by email, marking bills as paid and voiding payments, and none of them appears among the 12 MCP tools. The listed surface reaches reporting and reference data only, so nothing an agent calls leaves your organisation.
Three, with configurable periods. The income statement, balance sheet and cash flow statement tools map to Campfire API endpoints that split results by a cadence parameter into monthly, quarterly or yearly columns. Campfire also documents a trial balance, comparative statements and a general ledger report as REST endpoints with no MCP tool.
Sources
- Campfire MCP guide, "AI Integration with Model Context Protocol" (retrieved 2026-08-22, as Markdown via the
.mdsuffix) · retrieved 2026-08-22 - Campfire API quickstart, token minting and API-user roles (retrieved 2026-08-22) · retrieved 2026-08-22
- Campfire documentation index,
llms.txt(retrieved 2026-08-22; 447 API reference entries) · retrieved 2026-08-22 - Campfire API reference, List Chart Transactions (retrieved 2026-08-22) · retrieved 2026-08-22
- Campfire API reference, List Vendors (retrieved 2026-08-22) · retrieved 2026-08-22
- Campfire API reference, Get Balance Sheet, Get Income Statement and Get Cash Flow Statement — · · (retrieved 2026-08-22) · retrieved 2026-08-22
- Campfire API reference, Send Credit Memo (retrieved 2026-08-22) · retrieved 2026-08-22
- Campfire
robots.txt, carryingContent-Signal: ai-train=yes, search=yes, ai-input=yes(retrieved 2026-08-22). Synthesis of this documentation is expressly permitted by the publisher. · retrieved 2026-08-22 - Live auth posture check, 2026-08-22: anonymous
initializereturned HTTP 401 withwww-authenticate: Bearer resource_metadata="https://api.meetcampfire.com/.well-known/oauth-protected-resource/mcp"; RFC 9728 descriptor at that URL; authorization server metadata athttps://api.meetcampfire.com/.well-known/oauth-authorization-server· retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Campfire support — <mailto:support@campfire.ai> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Campfire
- Tools
- 12
- Domain
- api.meetcampfire.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.