FurlPay Docs
Open App
  • Introduction
  • Quickstart
  • For AI Agents
  • Monorepo
  • API Routes
  • Authenticationnew
  • Webhook Eventsnew
  • Error Codesnew
  • Rate Limitsnew
  • Agentic Payments (x402)
  • Agent Trust & Mandates (TAP)
  • CCTP Cross-Chainnew
  • LI.FI Swapsnew
  • FurlPay Travels (Travel MCP)
  • Solana Actions & Blinks
  • Claude Connectornew
  • AI Assistants
  • Stripe Crypto
  • Persona KYC
  • MiCA Roadmap
  • Security Posturenew
  • MPC & WebAuthn
  • Help Centernew
  • Getting Started
  • KYC Verification
  • Passkeys & Biometrics
  • Privacy & Data Protection
  • Transaction Statuses
  • Gasless Transfers
  • Deposits & Withdrawals
  • Managing Virtual Cards
  • Freezing & Unfreezing Cards
  • Declined Transactions
  • SDK & API Support
  • x402 Monetization Basics
  • Booking Travel
  • Travel Refunds & Cancellations

Resources

  • Changelog
  • System Status
  • OpenAPI Spec
  • Community
  • GitHub
Docs/Integrations/Claude Connector

Integrations

FurlPay connector for Claude

Connect your FurlPay account to Claude and ask about your money in plain language — balances across chains, spending, transactions, travel. Claude can also prepare payments and bookings, but it can never send money on its own: every financial action produces an approval link that you confirm with your passkey.

The one thing to know

Claude cannot autonomously move money through FurlPay. Money-moving tools create an intent and return a secure approval link. Settlement happens only after a human authenticates with a passkey in FurlPay. There is no tool, and no scope, that settles funds from a chat message.

Connect FurlPay to Claude

In Claude, open Settings → Connectors → Add custom connector and enter the FurlPay MCP endpoint:

text
https://furlpay.com/api/mcp

Claude discovers the authorization server automatically, registers itself, and sends you to FurlPay to sign in and approve access. You choose what to grant on the consent screen. In Claude Code:

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

What Claude can do (12 tools)

Read-only — answer questions, never change anything:

  • get_financial_overview — balances, recent transactions and cards in one summary.
  • get_wallet_balances — stablecoin balances per token and chain, with USD values.
  • list_transactions — recent transactions, filterable by category.
  • get_treasury_insights — spending by category over a period (burn rate, budgets).
  • get_wallet_risk — AML/risk screening of a destination address before you pay it.
  • get_swap_quote — best cross-chain stablecoin route and price (quoting moves nothing).
  • search_travel — stays payable in stablecoins.
  • list_trips — your upcoming, past and cancelled trips.

Prepare-only — draft an action for you to approve; they change no balances by themselves:

  • prepare_payment — drafts a USDC payment and returns an approval link. Capped at $10,000 per action through the connector. Does not send.
  • book_travel_link — returns a link where you complete and pay for a booking yourself. Does not book or charge.
  • create_invoice — creates a payment request others can pay you. Receives money; never sends it.
  • open_support_ticket — files a support ticket. Seed phrases, private keys and card numbers are stripped server-side if pasted.

Permissions you grant

  • profile:read — your name, email and account status.
  • wallets:read — balances and address risk screening.
  • transactions:read — transaction history and spending analytics.
  • travel:read — your trips and available stays.
  • payments:write — prepare payments and invoices for your approval. Not settlement.
  • travel:write — prepare bookings for your approval. Not booking or charging.

A connection that doesn't request a scope cannot even see the tools that need it. If you grant only read scopes, the payment tools are not listed to the model at all.

Security model

  • OAuth 2.1 with PKCE (S256 only). Claude is a public client — it holds no secret, so the PKCE verifier is the proof. Authorization codes are single-use, expire in 5 minutes, and a replay is rejected atomically even if it races the original.
  • Strict redirect allowlist. Codes are only ever sent to Claude's official callbacks or a loopback address (for CLI clients, whose port is assigned at runtime). Nothing else.
  • Human-in-the-loop for money. Financial tools return an approval link, never a settlement. Approval requires a passkey/biometric on your device.
  • Same guardrails as the apps. The connector calls FurlPay's own API routes as you — the same validation, rate limits, ownership checks and audit trail as the web and mobile apps. Every consent grant and token issue is audited.
  • Scoped, short-lived tokens. Connector tokens are distinct from browser sessions: a stolen web cookie cannot be used as a connector credential, and vice versa.

Disconnect and revoke

Remove the connector in Claude (Settings → Connectors → FurlPay → Remove). Access tokens are short-lived and expire on their own; removing the connector stops new ones from being issued. To cut access immediately from FurlPay's side, change your password or lock your account in Settings → Security, which invalidates existing sessions and connector tokens.

Privacy, terms and contact

  • Privacy policy: https://furlpay.com/legal/privacy
  • Terms of service: https://furlpay.com/legal/terms
  • Support: support@furlpay.com — or ask Claude to open a ticket for you.
  • Security disclosures: security@furlpay.com

FurlPay shares with Claude only what the tools you authorized return. FurlPay never sends your private keys, recovery phrase, card numbers or session tokens to any AI client — they are not reachable through any tool.

Did this page help?
Edit this page on GitHub

← Previous

Solana Actions & Blinks

Next →

AI Assistants