MercanPay MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERCANPAY_API_KEY | Yes | Your MercanPay API key (`mp_…` live or `mp_test_…` test key). Use a key with only the `invoices` and `read` scopes. | |
| MERCANPAY_BASE_URL | No | The base URL of the MercanPay REST API. | https://mercanpay.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_invoiceA | Create a payment request and get a hosted payment page (payment_url) to send to the customer. Either price_usd (customer picks TRX or USDT, rate locked) or token + amount (fixed coin amount). Minimum 10 USD. Use order_id to make it idempotent and to find it later. |
| get_invoiceA | Status and details of one invoice: pending, partial, paid, overpaid, expired or cancelled, amounts, payments and payment_url. |
| find_invoice_by_orderC | Look up the invoice created for one of your order ids. |
| list_invoicesA | Recent invoices, newest first. Filter by status; page with before (created_at of the last item). |
| cancel_invoiceA | Cancel an unpaid invoice so it can no longer be paid. Ask the user to confirm first. |
| simulate_paymentA | Test keys only: pretend the customer paid, paid part, overpaid, or let the invoice expire. Fires the same webhooks as real payments. |
| get_ratesA | Current USD prices of the supported coins (USDT and TRX), as used for USD-priced invoices. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| payment_request | Create an invoice for a customer and write them a short message with the payment link. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: create, retrieve one by id, find by order id, list, cancel, simulate, and rate lookup. The trio get_invoice / find_invoice_by_order / list_invoices could be momentarily confused, but descriptions clearly delineate id-lookup vs order-id-lookup vs paginated listing.
All tools follow a consistent snake_case verb_noun pattern (get_invoice, create_invoice, cancel_invoice, list_invoices, get_rates). find_invoice_by_order adds a qualifier but stays within the same convention and reads naturally.
Seven tools is well-scoped for an invoice/payments domain, covering creation, lookup, listing, cancellation, testing, and rates without redundancy. Every tool earns its place.
Core invoice lifecycle is covered (create, read, list, find, cancel) plus test payments and rate lookup. Minor gaps remain: no explicit refund or invoice-update operation, and nothing for webhook configuration or listing past payments at scale.