Skip to main content
Glama

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

create_payment_link

Bill someone and get a link they open to pay. Easiest way to get paid.

create_invoice

Create an invoice in a specific token and network, or bill in USD and get paid in crypto.

check_invoice

Paid or not, with the payment transaction.

list_invoices

Everything you've billed, paid and unpaid.

get_payment_transactions

For payers: the unsigned transactions to pay an invoice in their own wallet.

find_currency

Look up currency IDs like USDC-base or ETH-sepolia-sepolia.

Related MCP server: MercanPay MCP Server

Quick start

  1. 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.

  2. 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"
      }
    }
  }
}
  1. Ask: "Create a payment link for 25 USDC."

Configuration

Variable

Required

Purpose

REQUEST_CLIENT_ID or REQUEST_API_KEY

yes

Request Network credentials.

REQUEST_ORIGIN

with Client ID

Origin matching the Client ID's allowed domain.

REQUEST_DESTINATION_ID

for links

Your dashboard Route ID. Enables create_payment_link.

REQUEST_PAYEE

for create_invoice with an API key

Default wallet that gets paid.

REQUEST_API_URL

no

API base URL (default https://api.request.network).

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_transactions returns 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 build

License

MIT

Available Tools

6 tools
check_invoiceCheck an invoiceB
Read-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.

find_currencyFind a currency IDA
Read-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 invoiceA
Read-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 invoicesB
Read-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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Accept 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      2
      10
      648 npm
      MIT