Skip to content

Give Claude live access to Parallel.

Query stablecoin supply, check live yields and prepare transactions directly from Claude, Cursor, or any MCP-compatible client. No API key, no account, and the server never signs: writes come back as unsigned transactions your wallet reviews.

Connect the Parallel MCP server

claude mcp add --transport http parallel https://mcp.parallel.best/mcp

Any other MCP client: point it at https://mcp.parallel.best/mcp over Streamable HTTP.

Built to query, not to transact.

[01]

Live protocol data

Real-time stablecoin supply, TVL, backing, rates, chain status. Everything updates on demand.

[02]

Safe by default

Read-only by design. Writes return unsigned transactions that your wallet reviews and signs. The server holds no keys, no funds, no accounts.

[03]

Open ecosystem

Compatible with Claude Desktop, Cursor, Continue, Cline, and any MCP standard client.

Try these prompts in your agent.

The current sUSDp APY is 7.50%, protocol-wide across every chain with a Savings deployment.
Paid natively, with no lock-up and no cooldown
Earned by holding sUSDp; the rate is protocol-wide
Read straight from on-chain state, no API key involved.
USDp supply is $745,567, live across 5 chains:
hyperliquid l1: $438,674
ethereum: $199,786
avalanche: $93,939
base: $10,810
Plus 1 smaller deployments. Figures refresh daily.
The Parallelizer mints USDp at a 0% fee: 1,000 USDC gets you 1,000.00 USDp on Base.
Collateral: 1,000.00 USDC
Mint fee: 0.00%
You receive: 1,000.00 USDp

Works with every MCP client.

What people ask

It gives any MCP-compatible AI client live access to the Parallel stablecoin protocol (supply, yields, mint quotes, chain status) and builds transactions for savings, mint, redeem, bridge and staking. Writes come back as unsigned transaction data your own wallet reviews and signs.

Claude Code, Claude Desktop, Cursor, Cline, Continue, and any other client implementing the Model Context Protocol. There is nothing to install: point the client at https://mcp.parallel.best/mcp over Streamable HTTP.

Yes. There is no API key and no account. Read queries cost nothing; for write operations you pay only the on-chain transaction your own wallet signs and submits.

No. It holds no keys, no funds and no user accounts. Write tools return unsigned transaction data that your own wallet reviews, signs and submits; the server never signs or broadcasts anything.

The MCP server is the read-and-prepare layer for AI clients: it never signs, ever. The CLI is the terminal tool that can sign and broadcast when you explicitly hand it a wallet with --wallet. Same protocol underneath, different trust models for different jobs.

The write tool builds the exact calldata, simulates it pre-flight, and returns it unsigned with any warnings. Your wallet shows you what it does before anything touches the chain. Approve, and your wallet broadcasts it; refuse, and nothing happened.