Nerve RPC MCP — Nerve Blockchain for AI Agents
LocalAbout Nerve RPC MCP — Nerve Blockchain for AI Agents
Nerve RPC MCP exposes Nerve blockchain APIs for developers building AI Agent payment flows. It supports balance and transaction queries, address validation, and token swaps through NerveSwap; the repository also includes payment framework documentation and AI skills.
Key features
- 01Query Nerve balances and transactions
- 02Validate Nerve addresses
- 03Swap tokens through NerveSwap
- 04Support payment workflows
- 05Includes PayBox multi-chain payment skills
Use cases
- 01Check an address's received assets
- 02Prepare direct or swap-assisted payments
- 03Integrate PayBox cross-chain collections
MCP support
The MCP server exposes Nerve JSON-RPC and REST capabilities as tools for MCP clients, including queries used in payment flows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
14Saved tool list · updated 3w ago
This tool takes no parameters.
Details
From the project READMENerve Agent — AI Payment Framework & MCP
Nerve Agent payment framework and Nerve RPC MCP for developers and AI Agents: receive, pay, swap, and query balances. Decentralized protocol, locally generated and managed accounts, no gas fees, fast confirmation.
Also includes PayBox integration: accept payments from Ethereum, BSC, Polygon, TRON, NULS, NERVE — receive USDT on your Nerve address automatically.
- GitHub: NerveNetwork
- Website: nerve.network
Repository Structure
| Path | Description |
|---|---|
| agent-payment-framework/ | Payment framework docs: receiver / payer / PayBox / local accounts |
| nerve rpc mcp/ | Nerve RPC MCP server: exposes Nerve JSON-RPC / REST as MCP tools |
| nerveswap sdk/ | NerveSwap JS SDK and Nerve public API reference |
| .cursor/skills/nerve-agent-payment/ | AI Skill: Nerve receive, pay, balance, address, NerveSwap |
| .cursor/skills/paybox-payment/ | AI Skill: PayBox multi-chain collection via Nerve address |
Quick Start
1. Clone the repository
git clone https://github.com/NerveNetwork/nerve-agent.git
cd nerve-agent
2. Build and configure Nerve RPC MCP
cd "nerve rpc mcp"
npm install
npm run build
Add to your MCP client config (Cursor, Claude Desktop, etc.) — replace <PATH_TO_NERVE_AGENT>:
{
"mcpServers": {
"nerve-rpc": {
"command": "node",
"args": ["<PATH_TO_NERVE_AGENT>/nerve rpc mcp/dist/index.js"],
"env": {
"NERVE_API_BASE_URL": "https://api.nerve.network"
}
}
}
}
3. Install AI Skills
Skills are stored in .opencode/skills/ (OpenCode-native) and .cursor/skills/ (Cursor-compatible).
Project level (auto-loaded when you open this repo in OpenCode or Cursor):
git clone https://github.com/NerveNetwork/nerve-agent.git
# Skills are detected automatically in .opencode/skills/ and .cursor/skills/
User-wide (available in all your projects):
OpenCode / OpenClaw (native path)
mkdir -p ~/.config/opencode/skills/nerve-agent-payment
curl -o ~/.config/opencode/skills/nerve-agent-payment/SKILL.md \
https://raw.githubusercontent.com/NerveNetwork/nerve-agent/main/.opencode/skills/nerve-agent-payment/SKILL.md
mkdir -p ~/.config/opencode/skills/paybox-payment
curl -o ~/.config/opencode/skills/paybox-payment/SKILL.md \
https://raw.githubusercontent.com/NerveNetwork/nerve-agent/main/.opencode/skills/paybox-payment/SKILL.md
Cursor
mkdir -p ~/.cursor/skills/nerve-agent-payment
curl -o ~/.cursor/skills/nerve-agent-payment/SKILL.md \
https://raw.githubusercontent.com/NerveNetwork/nerve-agent/main/.cursor/skills/nerve-agent-payment/SKILL.md
mkdir -p ~/.cursor/skills/paybox-payment
curl -o ~/.cursor/skills/paybox-payment/SKILL.md \
https://raw.githubusercontent.com/NerveNetwork/nerve-agent/main/.cursor/skills/paybox-payment/SKILL.md
After installing, restart your AI client. Skills auto-load when relevant tasks are detected.
Also add a npx MCP config (after publishing to npm):
{
"mcpServers": {
"nerve-rpc": {
"command": "npx",
"args": ["-y", "nerve-rpc-mcp"]
}
}
}
Skills Overview
nerve-agent-payment
AI skill for Nerve blockchain payment integration.
Triggers automatically when: creating Nerve address, checking NVT balance, receiving crypto, paying on-chain, using NerveSwap, building Agent wallets.
Covers:
- Create / validate Nerve address (nerve-sdk-js, non-custodial)
- Query received amounts by asset (Nerve RPC MCP)
- Pay directly with address assets (NerveSwap SDK)
- Swap then pay (NerveSwap SDK)
- Local signing for Agent/server use
- MCP tools quick reference and setup
paybox-payment
AI skill for PayBox multi-chain payment collection.
Triggers automatically when: accepting payments from multiple chains, integrating PayBox, handling cross-chain collection, verifying PayBox webhook callbacks, querying PayBox orders.
Covers:
- Prerequisites: Nabox ID registration, collection address, callback URL
- Payment page invocation (testnet + mainnet URLs)
- Webhook signature verification (ECDSA, Java + TypeScript examples)
- Query APIs: chains, assets, price, order status
- Integration checklist
- TypeScript API client example
Capabilities Overview
- Receiver (Nerve): Create address locally → share → query received currency and amount via MCP.
- Payer (Nerve): Query assets via MCP → pay directly or swap via NerveSwap then pay.
- PayBox Merchant: Register Nabox ID → accept payments from 6+ chains → receive USDT on Nerve.
- Protocol: Decentralized; accounts generated and managed locally, keys never custodial.
- Nerve: Fast confirmation (~2s), no gas fees — suited for AI and high-frequency payments.
Links
- Nerve website
- NerveNetwork GitHub
- Agent payment framework
- PayBox flow
- PayBox API docs
- Nerve RPC MCP
- NerveSwap JS SDK
Pushing to GitHub
git remote add origin https://github.com/NerveNetwork/nerve-agent.git
git branch -M main
git push -u origin main
Add Topics: nerve, mcp, blockchain, agent, payment, nerveswap, paybox, cross-chain.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.