Integrations

FurlPay connector for Claude

Connect your FurlPay account to Claude over MCP and grant access to specific account tools. Claude can read authorized account data and prepare some actions for review. Payment settlement still depends on rail availability, and production travel booking is unavailable.

The one thing to know

A tool call is not proof that money moved. Payment tools can prepare an intent or request for user review. Production settlement depends on the selected rail being enabled and confirmed. Travel links open discovery; FurlPay production travel booking is not currently available.

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

Tools currently defined by the connector

The MCP server defines the tools below. Claude sees only tools allowed by the scopes you grant, and a tool result can still be limited by account data, provider configuration or payment-rail availability.

Read-only — answer questions, never change anything:

get_financial_overview — account overview data returned by the API.
get_wallet_balances — stablecoin balances per token and chain, with USD values.
list_transactions — recent transactions, filterable by category.
get_portfolio — read-only portfolio data when available; this tool does not place trades.
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 — hotel discovery results when a provider returns them; results are not bookable inventory.
list_trips — trip records returned for your account; this does not indicate that FurlPay booking is available.

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

prepare_payment — prepares a USDC payment for review, subject to the route's limits and authentication. Does not settle by itself.
book_travel_link — opens a travel discovery page. FurlPay production booking and payment are unavailable.
create_invoice — creates a payment request. It does not mean a recipient can complete settlement through FurlPay.
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 — trip records and travel discovery data when available.
payments:write — prepare payments and invoices for your approval. Not settlement.
travel:write — opens the travel discovery flow; it does not book or charge.

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.
User review for financial actions. Tools can return an approval link or request, but settlement still depends on rail status and the route's confirmation flow.
API route checks apply. The connector calls FurlPay's API as the signed-in account and is subject to route validation, authorization and rate limits.
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). To revoke authorization from FurlPay, use the account's connected-app or security controls if shown, or contact support. Do not assume removing a client-side connector instantly revokes every previously issued token.

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

FURL Token

AI Assistants

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

Tools currently defined by the connector

Read-only — answer questions, never change anything:

get_financial_overview — account overview data returned by the API.

get_wallet_balances — stablecoin balances per token and chain, with USD values.

list_transactions — recent transactions, filterable by category.

get_portfolio — read-only portfolio data when available; this tool does not place trades.

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 — hotel discovery results when a provider returns them; results are not bookable inventory.

list_trips — trip records returned for your account; this does not indicate that FurlPay booking is available.

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

prepare_payment — prepares a USDC payment for review, subject to the route's limits and authentication. Does not settle by itself.

book_travel_link — opens a travel discovery page. FurlPay production booking and payment are unavailable.

create_invoice — creates a payment request. It does not mean a recipient can complete settlement through FurlPay.

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 — trip records and travel discovery data when available.

payments:write — prepare payments and invoices for your approval. Not settlement.

travel:write — opens the travel discovery flow; it does not book or charge.

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.

User review for financial actions. Tools can return an approval link or request, but settlement still depends on rail status and the route's confirmation flow.

API route checks apply. The connector calls FurlPay's API as the signed-in account and is subject to route validation, authorization and rate limits.

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.

Privacy, terms and contact

Support: support@furlpay.com — or ask Claude to open a ticket for you.

Security disclosures: security@furlpay.com