Connect Claude to TreasuryFlow

MCP setup guide · updated June 2026

TreasuryFlow runs a Model Context Protocol (MCP) server. Connect it and Claude can read your live cash position, 13-week forecast, AR aging, and vendor spend — deterministic numbers, straight from your bank feeds, no copy-paste. Access is read-only: there are no tools that move money, edit transactions, or change anything. Every call is logged to an audit trail you can review.

What Claude can do: read cash, forecast, AR, vendor, and health data scoped to your account. What Claude cannot do: move money, create or edit anything, or see another tenant’s data. The mutate tools don’t exist on the server, so no prompt — however creative — can invoke one.
Questions: security@treasuryflow.ai
1

Mint an API key (Claude Code & Desktop only)

Connecting from claude.ai on the web? Skip this step — you’ll sign in with your TreasuryFlow account when Claude prompts you (OAuth), no key to copy.

In the portal, open Settings → Connected apps & API keys and create a key labeled for the device you’ll connect (for example “Claude desktop”). The key starts with tfmcp_ and is shown once — store it in a password manager. We keep only a hash. Keys are read-only scoped, rate-limited, and revocable in one click.

The same card lists every app you’ve connected via OAuth (like claude.ai) and every key you’ve minted, each with a one-click revoke — plus the audit trail of everything connected apps accessed on your account.

2

Add the connector in Claude

The server URL is https://app.treasuryflow.ai/mcp (streamable HTTP). Pick your client:

Claude.ai (web) — one click, no key. Go to Settings → Connectors → Add custom connector, paste the URL below, and click Add. When Claude asks you to authorize, sign in with your TreasuryFlow account (email/password or Google) and approve read-only access — that’s the whole flow.

https://app.treasuryflow.ai/mcp

The connection uses OAuth with PKCE: claude.ai never sees a password or an API key, the access it gets is the same read-only scope as everything else on this page, and you can disconnect it any time from Claude’s connector settings.

Claude Code (terminal) — one command:

claude mcp add --transport http treasuryflow \ https://app.treasuryflow.ai/mcp \ --header "Authorization: Bearer tfmcp_YOUR_KEY"

Claude Desktop — add this to claude_desktop_config.json (Settings → Developer → Edit Config):

{ "mcpServers": { "treasuryflow": { "command": "npx", "args": [ "mcp-remote", "https://app.treasuryflow.ai/mcp", "--header", "Authorization: Bearer tfmcp_YOUR_KEY" ] } } }

Any other MCP client connects the same two ways: OAuth (discovery starts at the server’s 401 response, dynamic client registration supported) or a bearer Authorization header with a tfmcp_ key.

3

Ask Claude about your cash

Once connected, Claude sees nine read-only tools. Things people actually ask:

  • “What’s our cash position right now, by company?”
  • “Walk me through the 13-week forecast — where does the balance dip after debt payments?”
  • “Which invoices are 60+ days overdue, and how much is at risk?”
  • “Which vendors crept up this quarter?”
  • For firms: “Which client runs out of cash first?”

Claude drafts the email, the board note, the client brief — with numbers it pulled from the same deterministic engine your dashboard uses, not numbers it guessed.

Read-only, by construction
Every tool declares readOnlyHint and the server ships zero mutate tools. Keys carry a read scope; a future write tool would be rejected for every existing key.
Every call audit-logged
Each tool call writes an audit row — which tool, when, from where, how long. “Show me everything Claude read this month” is one request away.
Revocable & rate-limited
Revoke a key — or disconnect the claude.ai connector — any time; access stops immediately. Per-key and per-account limits (60/min, 1,000/day) keep an over-eager agent from hammering your data.