TRON resource exchange for AI agents. 52 tools, 30 prompts, 21 resources.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
MERX
https://MERX.exchange
TRON infrastructure for AI agents.
66 MCP tools. Energy market across 6 providers. USDT/USDC/USDD payments. x402 v2 facilitator on TRON mainnet.
Documentation | API Reference | MCP Server
Table of contents
- What is MERX — TRON infrastructure for AI agents
- The problem — why TRON had no agent layer until MERX
- Platform overview — MCP, agent payment service, x402, GasFree, energy aggregator
- Quick start — 4 paths (web, REST/SDK, Claude Code plugin, MCP)
- What sets MERX apart — only complete agent stack on TRON
- Architecture
- API overview
- MCP server
- SDKs
- Real-time data
- Payment methods
- Standing orders and monitors
- Savings calculator
- Error handling
- Security
- Tested on mainnet
- Comparison with alternatives
- Documentation
- License
What is MERX
MERX is the infrastructure layer for AI agents and agentic networks on TRON. Where Stripe is infrastructure for web commerce and Cloudflare for the open web, MERX is the missing infrastructure layer that lets autonomous AI agents discover, transact, and operate on TRON without ever touching energy, bandwidth, or low-level blockchain mechanics.
The platform exposes one coherent stack: 66-tool MCP server, agent payment service for TRC-20 stablecoins, x402 v2 facilitator (the only TRON facilitator in the coinbase/x402 ecosystem registry), GasFree transfers via a MERX-deployed mainnet controller, dedicated TRON RPC node, A2A (Google, 7 skills) and ACP (BeeAI, 7 capabilities) protocol coverage, and a natural language Policy Engine powered by Anthropic Claude.
Underneath those agent surfaces sits an energy aggregator across 6 active
providers (CatFee, Netts, TronSave, iTRX, PowerSun, TEM) that routes resource
purchases to the cheapest source automatically -- so when an agent calls
send(), MERX estimates the energy required, buys only the deficit, and
broadcasts the transaction. The agent never holds TRX or thinks about energy.
Any AI agent running in Claude, LangChain, CrewAI, Vertex AI, AutoGen, or BeeAI can send payments and acquire resources on TRON through a single integration with MERX.
Three ways to plug an agent into MERX:
-
MCP server -- 66 tools for AI agents. Hosted SSE at
https://merx.exchange/mcp/sse(zero install) or local stdio vianpx merx-mcp. Works with Claude, GPT, Cursor, Windsurf, and any MCP-compatible client. -
Claude Code plugin -- one-line install for Claude Code. Auto-registers the MCP server, ships 6 slash commands and a
tron-agent-engineersub-agent. See Hovsteder/merx-claude-plugin. -
REST API + SDKs -- direct programmatic access for agents that aren't using MCP. JavaScript (
merx-sdkv2.1 on npm), Python (merx-sdkv2.1 on PyPI), or raw HTTP against/api/v1/(70+ versioned endpoints).
For human users, the web platform at merx.exchange remains available for manual energy trading, dashboard, deposits, and withdrawals -- but the platform is built primarily for agents.
The problem
AI agents will become the dominant transactional users of stablecoins, and TRON -- home to USDD, $86B+ USDT, USDC, and the dominant chain for retail USDT in Southeast Asia, Africa, and Latin America -- is already the largest USDT-native network in the world.
But TRON has no infrastructure designed for agents:
-
No agent-native payment service. Existing TRON wallets are built for human users with mouse clicks and seed-phrase backups, not for autonomous programs that need to register addresses, send TRC-20s, watch for incoming payments, and create invoices via REST.
-
Energy and bandwidth are a UX dead-end. Every smart contract call on TRON requires energy. Without energy, TRX tokens burn as fees -- a single USDT transfer burns 3-13 TRX (~$1-4) for cold receivers. Renting energy from a provider drops the cost to ~$0.10 -- a 94% reduction -- but every provider has a different price, different API, different duration tiers, and different failure modes. No agent can be expected to manage that.
-
No x402 facilitator on TRON before MERX. The x402 protocol has already processed $43.57M in agent-to-agent payments on Base, Solana, Stellar, and Ethereum. TRON was completely absent from the coinbase/x402 ecosystem registry until MERX. Agents that wanted to pay for TRON-hosted APIs in USDT had no standardized way to do it.
-
Three agent protocols, zero TRON integrations. MCP (Anthropic), A2A (Google), and ACP (BeeAI) are the three major agent communication protocols. Until MERX, none of them had a deployed, production-grade TRON server. AI agents in Claude, Vertex AI, or BeeAI literally could not see TRON.
MERX builds the missing layer. AI agents call one API, hold zero TRX, and get paid / pay / send / receive in USDT, USDC, or USDD on the world's largest USDT network.
| Without MERX | With MERX |
|---|---|
| Agent has to manage energy + bandwidth manually | send() estimates and provisions resources automatically |
| Agent has to hold TRX as gas | GasFree transfers — agents send stablecoins from zero-TRX wallets |
| Agent has to integrate every energy provider's API | One MERX API routes to the cheapest of 6 providers |
| No way to pay for TRON-hosted APIs in USDT | x402 v2 facilitator with full USDT/USDC/USDD support |
| No A2A/ACP discovery on TRON | Agent Card + Manifest live, 7 skills, 7 capabilities |
| Agent has to write its own MCP server for TRON | 66 tools, 30 prompts, 21 resources, hosted |
| Address watching means polling RPC | watch() with sub-3-second webhook delivery via ZMQ |
Platform overview
| Component | Description |
|---|---|
| MCP server | 66 tools, 30 prompts, 21 resources for AI agents. Hosted SSE at https://merx.exchange/mcp/sse (zero install) or local stdio. SEP-1649 server card. The largest TRON-native MCP server in production. |
| Claude Code plugin | One-line install: /plugin marketplace add Hovsteder/merx-claude-plugin. Auto-registers MCP, 6 slash commands, sub-agent. |
| Agent Payment Service | agent.merx.exchange -- non-custodial REST API. register, send, receive, watch, invoice, batch, schedule, contacts. USDT live; USDD/USDC next sprint. |
| x402 v2 Facilitator | x402.merx.exchange -- only TRON facilitator in the coinbase/x402 ecosystem registry. Three settlement schemes (exact, exact_permit, exact_gasfree) for USDT, USDC, USDD on TRON mainnet plus USDC on Base. |
| GasFree Transfer Service | Mainnet controller TKjJ1r5XYqnLZmLakcP3knis7Lh6gm3qtR activated 2026-04-08. TIP-712 PermitTransfer for USDT/USDC/USDD. Agents send stablecoins from zero-TRX wallets. |
| A2A Protocol (Google) | Agent Card at /.well-known/agent.json. 7 skills including compile_policy. Task-based execution with SSE streaming. Compatible with LangChain, CrewAI, Vertex AI, AutoGen, Mastra. |
| ACP Protocol (BeeAI) | Manifest at /.well-known/agent-manifest.json. 7 capabilities matching A2A skills. Run-based execution with long-polling. |
| Policy Engine | Natural language → standing orders, powered by Anthropic Claude Sonnet 4. Available as MCP tool, A2A skill, and REST endpoint. |
| Energy aggregator | Real-time price comparison across 6 active providers (CatFee, Netts, TronSave, iTRX, PowerSun, TEM). Routes orders to cheapest source. Underneath the agent surfaces. |
| Dedicated TRON RPC node | rpc.merx.exchange, sub-5ms read latency, 13.7ms broadcast. Trial 1,000 free requests; paid tiers with energy-spend waiver. |
| REST API | 70+ versioned endpoints under /api/v1/. Idempotency-Key on POST. Standard error format. |
| WebSocket | Real-time TRC-20 transfer stream and price updates at wss://merx.exchange/ws. |
| JavaScript SDK | merx-sdk v2.1 -- AgentModule + SwapModule + 4 base modules. TypeScript types included. |
| Python SDK | merx-sdk v2.1 -- same surface in snake_case. |
| x402 middleware | merx-x402 v2.0.0 -- one-line Express integration for x402 v2. |
| Documentation | 38+ pages at merx.exchange/docs. API reference, MCP/A2A/ACP guides, x402 integration. |
Quick start
Four paths depending on your use case. For AI agents, paths 3 and 4 are the primary surfaces. Path 1 (web) is for human operators; path 2 (REST/SDK) is for direct programmatic integration.
Path 1: Web platform (humans)
Go to merx.exchange. Sign in. Deposit TRX. Manage energy, agent API keys, and balance through the dashboard. No code required.
Path 2: REST API / SDK (programmatic)
Install the JavaScript SDK:
Use it in your application (replace merx_sk_your_key with your API key from merx.exchange):
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
3
Stargazers on the source repository.
npm downloads
604
Package downloads in the last 30 days.
Last commit
5mo ago
Most recent push to the default branch.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about MERX TRON Resource Exchange
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/merx-tron-resource-exchange)HTML Embed
<a href="https://allmcps.com/mcp/merx-tron-resource-exchange"><img src="https://allmcps.com/api/badge/merx-tron-resource-exchange?style=directory" alt="MERX TRON Resource Exchange on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
11/16 checks healthy over the last 46d
40Quality signal: Fair · 40/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools15/30
Adoption & activity5/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 3d ago via OSV.dev · merx-mcp (npm)
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.