SaaSFlow for AI agents

Assistants

Connect an assistant in a minute

The MCP server lives at mcp.saasflow.com and speaks OAuth, so a client needs nothing more than the URL. Nothing to install, and every client sees the same tools.

https://api.saasflow.com/mcp

https://api.saasflow.com/mcp

claude mcp add --transport http saasflow https://api.saasflow.com/mcp

{
  "mcpServers": {
    "saasflow": { "url": "https://api.saasflow.com/mcp" }
  }
}

{
  "mcpServers": {
    "saasflow": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.saasflow.com/mcp"]
    }
  }
}

raycast.com/saasflow/saasflow

Tools

What an agent can ask once connected

Over 90 read tools cover companies, accounts, transactions, customers, vendors, subscriptions, and every metric the dashboards show. The server tells the model to take metrics from the data tools instead of summing transactions itself, so answers match the app.

“What is our MRR today, and how did it move this month?”

data_mrrAtDate

“Which customers churned or downgraded in March?”

data_customerChanges

“Show me last quarter's P&L split by category.”

data_profitLossData

“Who are our ten biggest expense vendors this year?”

data_topExpenseVendors

“How long does the cash last at the current burn?”

data_cashFlowTimeSeries

“Find the Stripe payout from January 12 and show its transactions.”

search

“How does the 2025 cohort retain compared to 2024?”

data_cohorts

“What exactly is counted in net revenue retention here?”

data_metricExplanation

Full tool reference →

Developers

Build your own agent

Everything the MCP tools do is a REST call underneath. Use the API directly, script it with the CLI, or ship an app that users install with OAuth.

curl https://api.saasflow.com/companies/cmp_.../data/mrrAtDate \
  -H "Authorization: Bearer sf_live_..." \
  --get --data-urlencode "mrrType=cmrr" \
  --data-urlencode "date=2026-08-31"

npm install -g saasflow
saasflow login
saasflow data mrrAtDate --mrr-type cmrr --date 2026-08-31
saasflow transactions list --limit 20 --format table

npx openapi-typescript https://api.saasflow.com/openapi.json -o saasflow.d.ts

In the product

Agents that already run inside SaaSFlow

You do not have to bring your own model to get value from agents. Three run inside SaaSFlow today, and each can also be started through the API.

Each run executes in an isolated container with a credential that only lasts for that run. The models run on Google Cloud in the EU, the same provider that hosts SaaSFlow, and no other AI provider receives your data. More on security

Discovery

If you are an agent, start here

Every document a machine needs is at a stable, unauthenticated URL. Fetch these before guessing.

saasflow.com/llms.txt

What SaaSFlow is, when to use it, and where every page lives.

saasflow.com/agents.md

This page as Markdown.

docs.saasflow.com/llms.txt

Page-by-page index of the documentation. Append .md to any docs URL for its Markdown source.

api.saasflow.com/openapi.json

The OpenAPI 3.1 document, with the permission each operation needs.

api.saasflow.com/.well-known/mcp

MCP server card: the endpoint and what it accepts for auth.

api.saasflow.com/.well-known/api-catalog

RFC 9727 API catalog pointing at the same places.

document.modelContext

Browser agents on this site can call the WebMCP tools estimate_saasflow_price and estimate_saas_valuation instead of reading the pricing and valuation pages.

Permissions

What an agent can and cannot do

Scoped credentials

An API key belongs to one company and carries an explicit permission set. An OAuth grant is limited to the scopes you approve, intersected with your own role.

Read-only by default

Every OAuth connection starts with read tools only. Write tools appear when the grant carries the write scope, or when the caller uses an API key.

No admin access for agents

Managing users, API keys, integrations, and company settings stays with signed-in people. Neither API keys nor OAuth tokens can hold those permissions.

Revocation and audit

Revoking a key or a grant in Settings takes effect on the next request. Every tool call over the hosted endpoint is written to an audit log with the credential that made it.

Sandboxed built-in agents

The agents that run inside SaaSFlow execute in isolated containers with a run-scoped credential. They run on Claude, hosted by Google Cloud in the EU.

EU hosted, no money movement

SaaSFlow runs in the EU and reads from your billing and banking providers. Nothing here can initiate a payment.

Go deeper