DevelopersMCP
MCP server
Expose SaaSFlow as tools to Claude, ChatGPT, and other Model Context Protocol clients.
The SaaSFlow MCP server is published as @saasflow/mcp.
It exposes the SaaSFlow API as MCP tools so an LLM (Claude Desktop, ChatGPT,
custom clients) can read your subscription, cash, and P&L data.
Two ways to run it
| Mode | Use when |
|---|---|
| Stdio (local) | Claude Desktop, custom clients, scripts. Auth via API key in env var. |
| Remote (HTTPS) | Hosted clients like ChatGPT. Auth via OAuth bearer. |
In both modes, every tool is scoped to your company. Read tools are always available; write tools are opt-in (see Writes).
What's exposed
- Hand-written tools for the most common LLM tasks (browsing transactions, listing customers, search).
- Auto-generated tools — one per OpenAPI operation, skipping
dataandsearch(covered by hand-written tools). - One auto-generated
data_*tool per data slice for pre-aggregated analytics.
Full reference at MCP tools.
Writes
Write tools — create, update, and delete on every resource — are registered when writes are enabled:
- Stdio: set
SAASFLOW_MCP_WRITES=1in the server's environment. - Remote: connect with an API key, or with an OAuth token that has the
saasflow:writescope.
Writes are still bounded by the API key's permission set or the granting user's permissions — the MCP flag only controls which tools are registered. Without it, the server is read-only. See MCP tools for the full list.