Morpho MCP

Morpho MCP is Morpho's hosted, remote MCP server. It gives any MCP-compatible agent live access to Morpho vaults, markets, Midnight fixed-rate markets, and positions, and lets it prepare unsigned transactions for you to review and sign.

Setup and Usage

The server is hosted and public. There is nothing to install and no key to manage. It never signs or sends a transaction.

Most tools are generated from the Morpho API OpenAPI specs, one tool per API operation, so their inputs and outputs match the API reference. The conventions below apply to protocol calls:

• Generated tools take selectors. Single-vault tools and vault prepare tools take a vault-selector formatted as <chainId>:<vaultAddress>, for example 8453:0xbeef0e0834849aCC03f0089F01f4F1Eeb06873C9. Single-market Blue tools and market prepare tools take a market-selector formatted as <chainId>:<marketId>. Midnight market IDs are unique across chains, so Midnight tools take a market-id with no chain ID. List tools take filters, not a selector.
• Amounts are base units. Asset amounts are integer strings in the token's base units. Read token decimals from tool responses; never assume them. Share amounts (shares inputs or unit: "shares") are integer strings in raw onchain share units — vault shares, or Morpho Blue supply/borrow shares — not scaled to the asset's decimals.
• List tools are paginated. Pass the returned cursor back until it is null.
• Discover before you write. Find a target with a list tool, inspect it with the matching get tool, then call a morpho_prepare_* tool. Never hardcode addresses.
• Older tools take chain slugs. morpho_get_token_balance, morpho_prepare_claim_rewards, and the deprecated get and position tools take a chain slug. They accept only chains where morpho_get_supported_chains returns supportsRpcTools: true. The deprecated query tools also accept a numeric chainId.

Prepare tools

A generated morpho_prepare_* tool calls the Morpho Actions API and returns its result under data:

• If data.status is signature_required, sign each data.signatures[].typed_data, then call the same tool again with the same selector and the body { continuation, signatures: [{ id, signature }] }.
• A finished result lists the unsigned transactions in data.calls. Send them unchanged and in order from the account, and only if data.simulation.status is success and data.expires_at has not passed.
• If data.simulation.status is failed, show data.simulation.failure and do not send the calls.
• Each result carries action_proof, the Actions API's Morpho-Action-Proof response header. The MCP server passes it through without verifying it. Production clients must verify it against https://api.morpho.org/.well-known/morpho-actions-jwks.json (ES256 only) before showing typed data or sending calls.

morpho_prepare_force_redeem takes flat arguments (vault-selector, account, complete: true, max_penalty_bps) instead of a body, so it has no continuation call. Its result can report nonzero residual_shares, a safety margin the exit leaves in the vault; data.simulation.effects.remaining_shares shows the simulated balance left.

morpho_prepare_claim_rewards is not generated. It returns a PreparedOperation: the transactions to sign and a warnings array. Warnings carry a severity — an error means stop, and the transactions must not be presented for signing.

Setup Examples

Claude Code

Add the server with the claude mcp add command. The --scope user flag registers it once for every project on your machine; drop it to scope the server to the current project.

claude mcp add morpho --scope user --transport http https://mcp.morpho.org/

Confirm it connected:

claude mcp list

Inside a session, /mcp lists the connected servers and the tools each exposes.

Codex

Add the server with codex mcp add, passing --url to select the Streamable HTTP transport:

codex mcp add morpho --url https://mcp.morpho.org/

Confirm it connected:

codex mcp list

You can also declare the server in ~/.codex/config.toml to make it global, or in a trusted project's .codex/config.toml to scope it to that project:

[mcp_servers.morpho]
url = "https://mcp.morpho.org/"

[mcp_servers.morpho]
url = "https://mcp.morpho.org/"
tool_timeout_sec = 120

Other clients

Any MCP client that speaks the Streamable HTTP transport can connect by pointing at the endpoint. In Cursor, add it to .cursor/mcp.json:

{ "mcpServers": { "morpho": { "type": "http", "url": "https://mcp.morpho.org/" } } }

Tools

The server exposes 80 tools. Read tools answer questions about protocol state or the documentation; prepare tools return unsigned transactions.

General

Blue markets

Vaults V1

Vaults V2

Midnight

Transactions

Deprecated

These read tools still work but will be removed. Use the generated tools instead.

Response notes

Generated tools return APYs as decimal rates that exclude rewards: 0.0317 means 3.17%. The deprecated tools return percentage strings. Vault list tools return no APY or TVL; fetch each vault's state and APY tools before ranking vaults. Vault tools return the curator as an address, not a name.

For product implementation and review guidance, install the separate Morpho Skills.

Prompt Examples

Once the server is connected, ask in plain language. Your agent picks the tools.

1. For vault 0x… on Base, show its average APY, TVL, curator, and fee rates. Note that the APY excludes rewards.
2. Compare the borrow rates on the wstETH/WETH markets on Ethereum and Arbitrum.
3. For 0x… on Base, show my position in market 0x… and how much I have earned and paid.
4. List all my V2 vault positions across chains.
5. Prepare a 1,000 USDC deposit into vault 0x… on Base for 0x…, and show me the transactions before I sign anything.
6. How much can I withdraw from V2 vault 0x… on Ethereum right now, and what would a forced withdrawal cost?
7. List the Midnight markets and show the order book for the nearest maturity.
8. Do I have claimable Merkl rewards on Base? If so, prepare the claim.