MCP Gateway · Catalog
Campfire MCP server
OfficialCampfire MCP is the official Model Context Protocol server for Campfire, with API key authentication. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT can reach accounting, financial report, and ERP data through one governed URL, with SSO, RBAC, and a full audit trail.
Productivity0 toolsAuth: api key
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.
Tools
The registry has not published a tool list for this server yet. Behind the MCP Gateway it still gets SSO, role-based access, and an audit trail of every call.
Questions
What is a Campfire MCP server?
A Campfire MCP server exposes Campfire to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call its tools to work with Campfire. The server in this catalog is the official Campfire MCP server, which authenticates with an API key.
What can you do with Campfire MCP?
Agents can reach accounting, financial report, and ERP data. The registry has not published an individual tool list for this server yet, so no tools are shown on this page.
Why put Campfire MCP behind an MCP gateway?
Connecting the Campfire MCP server directly to each client means a separate credential per developer, no inventory of who can reach Campfire through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Campfire server, so sign-in runs through your identity provider, role-based access decides which teams can call which Campfire tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Campfire and to every other server in your catalog.
How do you connect Campfire MCP through a gateway?
Add the Campfire server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Campfire tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Campfire MCP?
Community-built Campfire MCP servers wrap the same Campfire surface but are not vendor-maintained. This catalog lists the official Campfire MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.