MERX TRON Resource Exchange
Give autonomous agents TRON energy and resource exchange capabilities on MERX—quotes, orders, balances, and wallet-signed transfers via a 54-tool MCP surface.
Overview
MERX MCP is an MCP server for the Build phase that lets AI agents trade and manage TRON energy and resources on MERX with 54 tools, 30 prompts, and 21 resources.
What is this MCP server?
- 54 MCP tools, 30 prompts, and 21 resources for TRON resource exchange
- Remote SSE/streamable-http at https://merx.exchange/mcp/sse
- npm stdio package merx-mcp v1.0.5 with MERX_API_KEY
- Optional TRON_PRIVATE_KEY for local signing without sending the key to servers
- Agent protocols A2A and ACP called out for multi-agent trading setups
Community signal: 3 GitHub stars.
What problem does it solve?
Building TRON energy automation means juggling exchange APIs, signing, and agent orchestration—too slow for a solo builder testing agentic trading ideas.
Who is it for?
Developers shipping TRON-focused agents, energy arbitrage experiments, or A2A/ACP trading stacks who already understand wallet security.
Skip if: Non-crypto products, beginners without key hygiene, or teams that only need read-only chain explorers.
What do I get? / Deliverables
After configuring MERX_API_KEY and optionally a local TRON_PRIVATE_KEY, your agent can quote, trade, monitor, and sign TRON transactions through MERX’s MCP tools.
- Agent-driven MERX quotes, orders, balances, and monitors
- Locally signed TRON transfers and contract calls when keyed
- Reusable prompts and resources across 54 exchange tools
Recommended MCP Servers
Journey fit
MERX is an external trading and wallet integration you wire in during Build, before you harden Ship security around keys and funds. It connects your agent stack to the MERX exchange and TRON chain, which is classic third-party integration work.
How it compares
TRON exchange and wallet-action MCP, not a static crypto price ticker skill.
Common Questions / FAQ
Who is exchange.merx/mcp for?
Solo builders and agent developers automating TRON resource and energy trades on MERX who want a large pre-built MCP tool layer.
When should I use exchange.merx/mcp?
Use it in Build while integrating MERX trading, standing orders, or wallet-signed flows into Claude Code, Cursor, or multi-agent A2A/ACP setups—before production Ship hardening.
How do I add exchange.merx/mcp to my agent?
Add remote MCP https://merx.exchange/mcp/sse or install npm merx-mcp 1.0.5 for stdio, set MERX_API_KEY from merx.exchange, and optionally TRON_PRIVATE_KEY in the local environment per the package docs on GitHub Hovsteder/merx-mcp.