Floe MCP Server

Connect Floe to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Credit and payments for AI agent developers. The floe mcp server is what makes that connection.

What the server does

65 tools covering the full agent lifecycle — create agents, mint/rotate keys, set budgets, estimate costs, and execute x402 payments — with transport-aware auth (remote HTTP uses a Bearer token; local stdio reads FLOE_API_KEY from the env) and a keyless tier (get_markets, check_x402_url, search_floe_docs work with no key at all).

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Group — Tools
• Webhooks — create_webhook, list_webhooks, test_webhook
• Docs — search_floe_docs (keyless)
• Wallet — get_wallet_balance, get_accrued_interest
• Utility — simulate_transaction, broadcast_transaction, get_transaction_status
• get_markets — List active lending markets with rates and liquidity (keyless)
• get_open_lend_intents — Browse lend offers available for borrowing against
• get_open_borrow_intents — Browse borrow requests from borrowers seeking lenders
• get_intent_details — Get full details of a specific intent by hash
• get_loan — Get loan details by numeric ID
• get_user_loans — Get all loans for a wallet (borrower + lender)
• get_loan_health — Check loan LTV, health status, liquidation risk

Credentials and setup notes

Configuration is passed through the environment: FLOE_API_KEY, YOUR_FLOE_KEY, FLOE_API_BASE_URL, PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Floe.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Floe's toolset — Group, Webhooks, Docs and 11 more — is a fair guide to whether it matches your workflow. It is maintained by floe-labs; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.