Skip to Content
SaaSFlow
DevelopersMCP

Connect a client

Add the SaaSFlow MCP server to Claude, ChatGPT, Cursor, or your own client.

Every client talks to the same server over HTTPS:

https://mcp.saasflow.com

Connectors set up with the earlier address, https://api.saasflow.com/mcp, keep working as they are.

Most clients only need that URL. They discover the auth flow from the endpoint itself (RFC 9728 metadata at /.well-known/oauth-protected-resource on the same host), identify themselves with a Client ID Metadata Document (Claude, ChatGPT) or dynamic client registration (Cursor and others), and send you to app.saasflow.com to sign in and approve.

No account yet? Create one on that sign-in page, with Google or with your work email. After you confirm your email, the connection continues to the consent screen.

Sign in

Clients sign in when they connect. The first request without a token answers HTTP 401 with a WWW-Authenticate header pointing at the resource_metadata URL, and the client starts sign-in from there. The metadata lists every scope, and clients that request what it lists get a consent screen with all the options. In Claude Code the server shows as needing authentication, and the model gets an authenticate tool for it, which returns a sign-in link to hand to you.

Signed in, a connection lists only the tools its token's scopes allow. If a client calls one the token doesn't cover anyway, the answer is 403 with error="insufficient_scope" and a scope listing everything the token holds plus what's missing (for a batch, what all its calls are missing), so clients that support step-up can ask you to sign in again with that option ticked. The API checks the token's scopes again on every call.

https://api.saasflow.com/mcp asks for sign-in the same way, without get_started.

In the app, the robot icon at the bottom of the sidebar shows the address with a copy button, and User settings → Connect AI has the setup steps below.

By client

ClientSetup
Claude (web, desktop, mobile)Settings → Connectors → Add custom connector, paste the URL.
ChatGPTAdd it as a connector. Same URL, same OAuth flow.
Claude Codeclaude mcp add --scope user --transport http saasflow https://mcp.saasflow.com
Cursor{ "mcpServers": { "saasflow": { "url": "https://mcp.saasflow.com" } } } in .cursor/mcp.json
Your own clientStreamable HTTP transport, bearer auth. See OAuth for apps.

A client that speaks only stdio can bridge to the endpoint:

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

mcp-remote is a third-party bridge, not a SaaSFlow package.

OAuth

FieldValue
Authorization endpointhttps://api.saasflow.com/auth/oauth2/authorize
Token endpointhttps://api.saasflow.com/auth/oauth2/token
Resourcehttps://mcp.saasflow.com, or the URL you connected to (https://mcp.saasflow.com/mcp, https://api.saasflow.com/mcp)
Scopessaasflow:read, saasflow:write, saasflow:admin, saasflow:create_companies

Issued tokens have the resource as their audience, and any of the three works on every MCP address. SaaSFlow stores the consent grant; disconnecting the app under User settings → Connected apps invalidates the token in real time.

ScopeGrants
saasflow:readAll :read permissions, intersected with your user permissions.
saasflow:writeReads + :write permissions.
saasflow:admincompany:manage and integrations:manage: company settings, disconnecting integrations, switching accounts to manual. Also lets the agent ask you to approve member, API key and company deletion changes, which it never makes itself.
saasflow:create_companiesCreating companies with you as owner (companies_create). Ticking it accepts the Terms of Service and the Data Processing Agreement on behalf of each company the app creates.

saasflow:read is enough for questions and analysis. Write tools are registered only when the token carries saasflow:write.

On the consent screen, read access is always included. Write, admin and company creation are separate checkboxes. They start ticked when your account is less than a day old (you signed up to connect this app) and unticked otherwise; you can change each one before you allow. Tick Make changes to company data to grant saasflow:write, Manage company settings and integrations to grant saasflow:admin, and Create companies for you to grant saasflow:create_companies. Every scope stays bounded by your role: a viewer who ticks write and admin still can only read. Admin tools are listed only when the token carries saasflow:admin, and companies_create only when it carries saasflow:create_companies. To change it later, disconnect the app and connect again.

An app asks for saasflow:admin and saasflow:create_companies by name; neither is ever part of the default set.

API keys

For scripts, CI, and clients that would rather send a fixed header than run a browser flow, pass an API key as the bearer token:

Authorization: Bearer sf_live_...

A key belongs to one company, so tool calls can omit companyId. Write tools are registered, bounded by the key's permission set.

Get a token for testing

The saasflow CLI can mint an OAuth bearer:

saasflow login
# Then to print a fresh access token:
saasflow whoami --json | jq -r '.oauth.accessToken'

Useful when wiring up a custom MCP client.

Revoke

Open User settings → Connected apps in the SaaSFlow app. Every app you connected with OAuth is listed there, and disconnecting is immediate. API keys are revoked under Settings → API keys.

On this page