req-invoice-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@req-invoice-mcp Create a payment link for 25 USDC for the website redesign."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
req-invoice-mcp
Let your AI assistant send crypto invoices and tell you when they're paid.
An MCP server for Request Network: any MCP-capable assistant (Cursor, VS Code, Windsurf, desktop AI apps, your own agent) can create invoices, share payment links and check payment status in plain language.
"Invoice Acme 500 USDC for the website." "Has Acme paid yet?"
It holds no wallet and can't spend money. It creates and reads invoices only. Payers pay from their own wallet.
📖 Docs: https://becomingmountains.github.io/req-invoice-mcp/ (source in site/)
Unofficial community project. Not affiliated with or endorsed by Request Network.
Tools
Tool | What it does |
| Bill someone and get a link they open to pay. Easiest way to get paid. |
| Create an invoice in a specific token and network, or bill in USD and get paid in crypto. |
| Paid or not, with the payment transaction. |
| Everything you've billed, paid and unpaid. |
| For payers: the unsigned transactions to pay an invoice in their own wallet. |
| Look up currency IDs like |
Related MCP server: MercanPay MCP Server
Quick start
Get a free Client ID. Sign in at dashboard.request.network with your wallet, set up a receiving route (network, wallet, token), then Manage → Client IDs → Generate. Copy the Route ID too.
Add the server to your MCP client (Node 20+):
{
"mcpServers": {
"req-invoice": {
"command": "npx",
"args": ["-y", "github:becomingmountains/req-invoice-mcp"],
"env": {
"REQUEST_CLIENT_ID": "your-client-id",
"REQUEST_ORIGIN": "https://your-allowed-domain.example",
"REQUEST_DESTINATION_ID": "0xYourWallet@eip155:1#ABCD1234:0xTokenAddress",
"REQUEST_PAYEE": "0xYourWallet"
}
}
}
}Ask: "Create a payment link for 25 USDC."
Configuration
Variable | Required | Purpose |
| yes | Request Network credentials. |
| with Client ID | Origin matching the Client ID's allowed domain. |
| for links | Your dashboard Route ID. Enables |
| for | Default wallet that gets paid. |
| no | API base URL (default |
Testing on Sepolia
Use a fresh wallet. Set up a Sepolia receiving route in the dashboard, get test ETH from a Sepolia faucet and test USDC from faucet.circle.com, then create a link, pay it and run check_invoice.
Safety
No private keys, no signing, no sending. Nothing in this server can move funds.
get_payment_transactionsreturns unsigned transactions for the payer to review in their own wallet.Inputs are validated before any API call (addresses, amounts, IDs), so a confused model can't reach other API paths.
Credentials stay in your MCP client's config and are never echoed back in tool output.
Development
npm install
npm test # unit + MCP round-trip tests against a fake API
npm run buildLicense
MIT
Available Tools
6 toolscheck_invoiceCheck an invoiceBRead-only
Check whether an invoice has been paid, with the payment transaction(s) if it has.
Inputs: requestId (required).
create_invoiceCreate an invoiceA
Create an on-chain invoice (a "request") for a specific amount, currency and network. paymentCurrency picks the token and network, e.g. "USDC-base", "USDC-mainnet", "ETH-sepolia-sepolia" (use find_currency to look IDs up). invoiceCurrency is what the amount is denominated in; it defaults to paymentCurrency, or use "USD" to bill a dollar amount paid in crypto. Returns the invoice ID.
Inputs: amount (required), paymentCurrency (required), payee, payer, +2 more.
create_payment_linkCreate a payment linkA
Bill someone and get a link they can open to pay in their own wallet. Uses the network and token of the receiving route set up in the Request Network dashboard (REQUEST_DESTINATION_ID). The amount is in that route's token. This is the easiest way to get paid.
Inputs: amount (required).
find_currencyFind a currency IDARead-only
Look up Request Network currency IDs to use as paymentCurrency, e.g. symbol "USDC" on network "base" or "sepolia".
Inputs: symbol, network.
get_payment_transactionsGet transactions to pay an invoiceARead-only
For the PAYER: returns the unsigned transaction(s) needed to pay an invoice (a token approval, if needed, then the payment). This server never signs or sends anything; the payer reviews and signs them in their own wallet.
Inputs: requestId (required), payerWallet.
list_invoicesList invoicesBRead-only
List invoices created with these credentials, newest first, with paid/unpaid status.
Inputs: limit, offset, walletAddress.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a reasonably distinct role, but create_invoice and create_payment_link both 'bill someone' and could be confused at first glance, and get_payment_transactions vs check_invoice both surface payment transactions from different perspectives (payer vs payee). The descriptions do clarify these boundaries well, keeping overlap low.
All names are snake_case verb_noun, which is consistent. Minor deviation in verb choice for reads (get_payment_transactions, find_currency, check_invoice, list_invoices) rather than a single read verb, but the pattern remains predictable.
Six tools is a well-scoped surface for an invoicing server: create, pay, look up currency, check status, and list. Each tool clearly earns its place with no filler.
The core lifecycle (create invoice/link, obtain payment transactions, check paid status, list) is covered. Gaps remain around canceling/voiding an invoice, retrieving full invoice details by ID, and refunds, but agents can work around these for the primary pay-and-verify flow.
Maintenance
Related MCP Connectors
Invoicing for businesses and AI agents: invoices, crypto payments, compliance, Invoice Passports.
Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.
Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.
Create invoices from your AI assistant in 6 languages and 10 currencies, ready for WhatsApp.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAccept crypto payments from AI agents: create an invoice in one call and get a hosted checkout link (USDC/USDT on Celo, Base, Arbitrum, Polygon, BSC). No API key, instant self-custody settlement.MIT

MercanPay MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to create, look up, list, and cancel crypto invoices, manage reusable payment links, check USDT and TRX rates, and simulate test payments through a secure API.7MIT
sattle.me assistantofficial
AlicenseNot gradedqualityBmaintenanceEnables merchants to preview, create, list, and track invoices with line items, VAT, payment links, due dates, and PDFs using an assistant secret key, while ensuring payments go to the merchant's wallet and never spend funds.MIT
stablevoy-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to create USDT and USDC invoices, retrieve payment links, and check invoice and store payment status across connected payment-gateway stores via the Model Context Protocol.210648 npmMIT