Skip to main content
The yield.xyz MCP server exposes yield discovery, diligence, transaction building, and portfolio tracking as 22 typed tools that any Model Context Protocol client can call directly inside a conversation. Point Claude, Cursor, or another MCP-compatible agent at one endpoint and it works with live APYs, TVL, balances, and chain-correct unsigned transactions instead of guessing at request shapes.

Endpoint and transport

The server listens at https://mcp.yield.xyz/mcp over Streamable HTTP. It only accepts POST; a GET to the same path returns 405 rather than opening a legacy SSE stream. Verify it’s live before wiring it into a client:
A client that only supports local stdio servers connects through the mcp-remote bridge shown below rather than talking to the endpoint directly.

Authentication and access

Without a key, requests run against a shared service key and are metered per tool on a 24-hour rolling window: read tools per caller IP, wallet tools per wallet address. Over quota, any metered tool accepts an x402 micropayment per call, or you can wait for the window to roll: x402 payments settle in USDC on Base, or USDC, USDT0, or USDG on X Layer. submit_hash and the five documentation tools carry no quota at all. Set your own key with the x-api-key header on any transport, or an ?api_key= query parameter on the POST endpoint for clients that can’t set headers. A key you supply bypasses every quota and the x402 gate entirely; usage is billed to your own account instead. Get one from Projects & API keys. Machine-readable pricing and tier data are also published at https://mcp.yield.xyz/.well-known/x402.

Connect a client

Any MCP client that can add a remote Streamable HTTP server takes the endpoint directly. A client that only supports stdio needs the mcp-remote bridge. This is the config the yield-xyz-agentkit plugin registers:
If your client is Claude Code, installing the yield-xyz-agentkit plugin registers this connection for you instead of editing config by hand.

Tool reference

The server registers 22 tools, grouped by job. Each yields, actions, transactions, networks, and providers tool maps to one Yield API endpoint; the docs tools read the live documentation and OpenAPI spec. Inputs marked required must be present; everything else is optional. Paid marks the four wallet-execution tools metered as described in Authentication and access.
Always call yields_get before actions_enter or actions_exit, and yields_get_balances before actions_manage. A yield’s own mechanics.arguments schema is the authority on which fields it needs; never hardcode arguments from another yield. actions_enter, actions_exit, and actions_manage never sign or broadcast: sign the returned transactions in stepIndex order and report each hash with submit_hash. See Guardrails.

Yields

Actions

Transaction-building tools never sign or broadcast; they return unsigned transactions for your own signer.
actions_enter, actions_exit, and actions_manage all return the same action object:
Each entry in transactions[]:

Transactions

Networks & providers

networks_get_all returns the full list, narrowed by search or category; providers_get_all paginates with limit/offset.

Docs

Builder-facing tools for developing an integration; not for live yield data or user transactions.

Next steps

AgentKit for Claude Code

Install the plugin that registers this connection automatically.

Guardrails

Rules an agent follows before it signs or broadcasts anything.

Agent skills

Install yield.xyz capability into agents outside Claude Code.

Yield API reference

The REST API behind every tool.