Connect
- Server URL:
https://api.satora.io/mcp - Transport: Streamable HTTP
- Authentication: No API key or wallet connection required for these tools.
satora, select
Streamable HTTP, and enter the server URL above. Configuration file formats vary
by client; use its remote MCP server instructions. The client handles protocol
negotiation and tool discovery.
For self-hosted Satora deployments, use your API base URL followed by /mcp.
The endpoint runs in the main daemon and requires a version containing MCP
support.
These tools provide information only. They cannot create, fund, sign, claim,
or refund a swap. Use the SDK integration to execute swaps.
Never provide a seed phrase or private key to the MCP server.
Available tools
All five tools are marked read-only. Tool results include
structuredContent
for programmatic use and text content for clients that display text results.
Discover assets and routes
Start withlist_tokens and list_swap_pairs. Use the returned chain and token
identifiers when requesting a quote. Bitcoin-side identifiers include
Bitcoin, Lightning, and Arkade; EVM identifiers are chain ID strings, such
as "137" for Polygon. EVM token identifiers are contract addresses; Bitcoin
uses "btc".
A configured route does not guarantee current liquidity. Request a quote for
the intended amount before presenting an estimate to a user.
Discover CCTP and LayerZero bridge routes
Calllist_bridge_capabilities to discover Satora’s bridge support beyond the
direct routes returned by list_swap_pairs. Both bridge families settle through
Arbitrum (chain_id: "42161"):
- CCTP: USDC payouts to supported destination chains and inbound USDC funding from supported foreign chains. Solana inbound funding uses the SDK’s separate Solana signer flow. Ethereum, Polygon, and Arbitrum inbound funding use the SDK’s direct path and are excluded from the inbound CCTP list.
- LayerZero OFT: USDT0 payouts to supported destinations, with native USDT on Ethereum. Native USDT payouts to Tron appear only when the deployment’s adapter is configured and verified. This tool does not advertise LayerZero inbound funding.
outbound.bitcoin_sources and outbound.destinations, plus
inbound.sources and inbound.bitcoin_destinations. Directions are filtered by
the deployment’s enabled Bitcoin/Lightning/Arkade routes to and from Arbitrum;
disabled directions have empty arrays. Chain entries include the asset’s symbol,
token address and decimals, address format, and the protocol-specific domain or
endpoint ID. chain_id is an EVM chain ID string, or null for Solana and Tron.
CCTP domain IDs and LayerZero endpoint IDs are not EVM chain IDs.
The result explicitly sets mcp_quote_supported and mcp_execution_supported
to false and points to @satora/swap. Use that SDK for bridge quotes and
execution; do not pass these foreign-chain identifiers to get_swap_quote.
Discovery reports configured capabilities, not live liquidity, fee estimates,
pause status, or a guarantee of settlement. Obtain a fresh SDK quote.
Request a quote
get_swap_quote accepts these arguments:
Supply exactly one of
source_amount or target_amount. Amounts use satoshis
for Bitcoin and raw token units for EVM assets. For example, "100000" means
100,000 satoshis for BTC; "1000000" means one token for a token with six
decimals. Read decimals from discovery and preserve amounts as integer strings
to avoid floating-point rounding.
Example tool arguments for a Bitcoin-to-Polygon-USDC quote:
list_bridge_capabilities to discover those SDK routes.
Check swap status
Callget_swap_status with a UUID supplied by the user:
statuses as an object with id and status; an unknown UUID appears in
not_found. An invalid UUID is a tool error. See the
swap state machine for status meanings.
Anyone who knows a swap UUID can look up its status. This tool returns no
addresses, invoices, secrets, or wallet history, and provides no way to list a
user’s swaps.
HTTP example
An MCP client normally handles these exchanges. For a manual request, the following example initializes protocol version2025-11-25, which the endpoint
supports. Check the returned protocolVersion and use that negotiated version
on subsequent requests.
Mcp-Session-Id
is needed, and persistent SSE sessions are not offered. Other negotiated
protocol versions can have additional metadata requirements; use a compatible
MCP client for those versions.
Errors and limits
Check both the HTTP response and the MCP result. A tool can return HTTP 200 withresult.isError: true. API handler failures include an error message
and a numeric status in result.structuredContent. Protocol errors, such as
an unknown method, use the JSON-RPC error field. Internal service details are
redacted.
The endpoint allows 120 requests per minute per caller IP, limits request bodies
to 16 KiB, and applies a 30-second handler timeout. Avoid frequent status
polling and back off when you receive HTTP 429.
Browser requests carrying an Origin header are rejected by default. A native
or server-side MCP client without that header can connect. Operators can permit
specific browser origins with MCP_ALLOWED_ORIGINS; a browser integration
requires an allowed origin on its target deployment.
Self-hosted configuration
The endpoint uses the daemon’s public API listener. Configure these comma-separated environment variables before starting the daemon:MCP_ALLOWED_HOSTS: permitted request hosts. Defaults toapi.satora.io,localhost,127.0.0.1,::1. Set your deployment’s hostname and preserveHostin the reverse proxy. An empty value retains the defaults.MCP_ALLOWED_ORIGINS: permitted browser origins, for examplehttps://your-app.example:443. By default, every request with anOriginheader is rejected. Requests without that header are accepted subject to the other endpoint checks.