MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.
Most developer tooling work still happens through a UI a human drives. MCP MCP server moves it into the conversation instead. MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.
Model Context Protocol (MCP) server for Pear Protocol. Gives Claude, or any MCP-compatible agent, access to markets, pair ratios, positions, orders, trade history, portfolio, and (v0.2) full trade execution on Hyperliquid.
Pear is a Hyperliquid-backed perps platform for pair markets: long one basket against another. Every pair has a live ratio that moves as the legs diverge. More at pearprotocol.io.
The server publishes 14 tools. What each one is for:
get_health — API health and uptimelist_markets — browse pair markets with filters and paginationget_active_markets — top gainers, losers, and highlighted pairsget_pair_ratio — current ratio, 24h change, and funding for a specific pairget_account_summary — your account headerget_open_positions — your open positions with PnLget_open_orders — your open limit, TP, and SL ordersget_twap_orders — your active TWAP ordersget_trade_history — your closed trades with realized PnLget_portfolio — bucketed PnL across 1d, 1w, 1m, 1y, and all-timeget_agent_wallet — the agent wallet Pear uses to sign your tradescreate_agent_wallet — create the agent walletConfiguration is passed through the environment: PEAR_API_KEY, PEAR_ADDRESS, PEAR_REFRESH_TOKEN, PEAR_API_BASE_URL, PEAR_CLIENT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @marvelcodes/mcp-pear, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — get_health, list_markets, get_active_markets and 11 more — is a fair guide to whether it matches your workflow. It is maintained by MarvelNwachukwu; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_health | API health and uptime |
| list_markets | browse pair markets with filters and pagination |
| get_active_markets | top gainers, losers, and highlighted pairs |
| get_pair_ratio | current ratio, 24h change, and funding for a specific pair |
| get_account_summary | your account header |
| get_open_positions | your open positions with PnL |
| get_open_orders | your open limit, TP, and SL orders |
| get_twap_orders | your active TWAP orders |
| get_trade_history | your closed trades with realized PnL |
| get_portfolio | bucketed PnL across 1d, 1w, 1m, 1y, and all-time |
| get_agent_wallet | the agent wallet Pear uses to sign your trades |
| create_agent_wallet | create the agent wallet |
| set_risk_parameters | set or update TP and SL |
| PEAR_API_KEY | for auth tools |
{
"mcpServers": {
"pear": {
"command": "npx",
"args": ["-y", "@marvelcodes/mcp-pear@latest"],
"env": {
"PEAR_API_KEY": "your-pear-api-key-here",
"PEAR_ADDRESS": "0xYourWalletAddress"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PEAR_API_KEY | Credential the server authenticates with. | Yes |
| PEAR_ADDRESS | Configuration value read at startup. | Optional |
| PEAR_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| PEAR_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| PEAR_CLIENT_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.