Cover photo

The Parallel MCP server is live

Live protocol data and ready-to-sign transactions, in any AI client

At a glance: One URL. Point Claude, Cursor, or any MCP client at it and ask about Parallel in plain language. You get live on-chain data, and transactions that your own wallet reviews and signs. The server never signs.

When we launched Parallel x402, we gave AI agents a way to pay. Today we're giving AI assistants a way to read the protocol and prepare transactions on it. The Parallel MCP server is live.

What it is

MCP, the Model Context Protocol, is how AI assistants connect to outside tools. The Parallel MCP server puts the whole protocol behind a single public URL. Connect Claude Code, Claude Desktop, Cursor, Continue, Cline or any client that implements the standard, and it gets 36 tools covering everything Parallel does.

Read tools return live on-chain data: TVL, USDp supply per chain, the sUSDp savings rate, backing and the proof-of-solvency ratio, mint and redeem quotes, bridge quotes, staking positions, chain status. Write tools build transactions for savings deposits and withdrawals, mint, redeem, bridge transfers and staking.

You ask in plain language and the assistant picks the right tools:

Give me a full overview of the Parallel Protocol

What's the current sUSDp savings rate?

Quote me a mint of 500 USDp with USDC on Base

Deposit 100 USDp into savings on Base, receiver 0xYourAddress

The first three are reads. The last one comes back as an unsigned transaction, plus an approval if one is needed, ready to review and sign in your wallet.

It never signs

This is the design decision that matters most.

The server holds no keys, no funds and no user accounts. Every write tool builds the exact calldata, simulates it before returning, and hands it back unsigned with any warnings attached: slippage, penalties, boosts you would lose. Your wallet shows you what the transaction does before anything touches the chain. Approve, and your wallet broadcasts it. Refuse, and nothing happened.

Because there is nothing to steal, there is nothing to configure. No API key, no account, no private key. The endpoint is public and unauthenticated by design.

This is the right trust model for an assistant. An AI that can read everything and prepare anything, but can move nothing without a human signature, is one you can hand to anyone.

Connect in two minutes

Claude Code, one command:

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

Claude Desktop: add this to claude_desktop_config.json and restart the app:

{

  "mcpServers": {

    "parallel": {

      "command": "npx",

      "args": ["-y", "mcp-remote", "https://mcp.parallel.best/mcp"]

    }

  }

}

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

Where it fits

Parallel now has three surfaces for agents and the people building them.

Parallel x402 is the payment rail. An agent with a funded wallet pays for APIs per call, gasless, in USDp, sUSDp or USDC.

The MCP server is the read-and-prepare layer for AI assistants. It never signs.

The Parallel CLI is the terminal tool that can sign and broadcast, when you explicitly hand it a wallet. Same protocol underneath, different trust models for different jobs.

For builders

If you're building assistants or agents that need to understand a stablecoin protocol, or you want to see what 36 tools can do, start here:

About Parallel

Parallel is a capital-efficient, modular, over-collateralized and decentralized stablecoins protocol, backed by yield-generating correlated assets.

DApp I Discord I X I Docs