MCP server
Expose SaaSFlow as tools to Claude, ChatGPT, and other Model Context Protocol clients.
SaaSFlow runs a hosted MCP server at https://api.saasflow.com/mcp. It exposes the
SaaSFlow API as MCP tools so an LLM (Claude, ChatGPT, Cursor, your own client) can read
your subscription, cash, and P&L data. Nothing to install: add the URL to your client
and sign in.
See Connect a client for the per-client setup.
Transport and auth
| Endpoint | https://api.saasflow.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 (dynamic client registration, PKCE) or a SaaSFlow API key as a bearer token |
Every tool is scoped to one company. Read tools are always available; write tools are opt-in (see Writes).
Clients and registries can discover the server from the card at
https://api.saasflow.com/.well-known/mcp
(mirrored at /.well-known/mcp on this site): the endpoint and its
auth requirements.
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 the
caller connects with an API key, or with an OAuth token carrying the saasflow:write
scope. Without either, the server is read-only.
Writes are still bounded by the API key's permission set or the granting user's permissions. See MCP tools for the full list.