@payre/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYRE_BASE_URL | No | Payre server URL. Defaults to https://payre.onrender.com | https://payre.onrender.com |
| PAYRE_SECRET_KEY | Yes | Your live merchant Secret API Key (starts with sk_live_...). Required. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Get details of the currently authenticated merchant profile, including tier, KYC status, compliance limits, and active business context. |
| list_businessesA | List all business contexts configured under the merchant account with their payout wallet addresses and domain verification status. |
| get_businessB | Get full details of a specific business context by UUID. |
| get_active_businessA | Retrieve the currently active business context used as default for invoice generation. |
| create_businessB | Create a new business context for receiving direct crypto payments. |
| update_businessB | Update an existing business context name, payout wallets, or domain. |
| delete_businessB | Delete a business context by UUID. |
| switch_active_businessC | Switch the active business context (used as default for checkout invoice generation). |
| create_invoiceA | Create a new payment checkout invoice and generate the buyer checkout URL. |
| list_invoicesA | List invoices created by this merchant, with pagination. |
| get_invoice_detailsA | Get full details of a specific invoice including active payment deposit sessions and payment transactions. |
| delete_invoiceC | Cancel or delete an invoice by UUID. |
| list_transactionsB | List payment transaction records and ledger settlements associated with the merchant account. |
| get_merchant_statsA | Retrieve volume analytics, invoice counts (paid/pending/expired), net revenue, and compliance tier limits usage. |
| list_chainsA | Retrieve configured EVM and Solana chains and their active payment currencies/tokens. |
| get_webhook_deliveriesB | Fetch webhook delivery attempt logs for a specific invoice. |
| get_webhook_secretA | Retrieve merchant webhook HMAC signing secret used for verifying webhook callbacks. |
| regenerate_api_keysA | Regenerate public (pk_live_...) and secret (sk_live_...) API keys for the merchant account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-crypto-invoice | Generate a Payre payment checkout link for a customer order with automatic chain selection. |
| check-account-status | Inspect current merchant balance, compliance tier limits, and latest payment transactions. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Supported Blockchains and Tokens | Documentation of active EVM and Solana chains, contract tokens, and settlement times on Payre. |
| Authenticated Merchant Profile | Live profile data, verification tier, and active business context for this account. |
| Merchant Volume & Performance Statistics | Revenue totals, paid invoice counts, and rolling tier limit usage. |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action. Business-related tools (list, get, create, update, delete, switch) are clearly separated, and invoice, transaction, stats, chain, webhook, and key tools have unambiguous purposes.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, get_business, list_transactions). There are no mixed conventions or vague verbs.
With 18 tools, the server covers merchant profile, business management, invoices, transactions, stats, chains, webhooks, and API keys. Each tool serves a clear function without redundancy or excessive bloat.
The server provides comprehensive coverage of merchant payment workflows including business CRUD, invoice lifecycle, transactions, stats, and webhook introspection. Minor gaps like lack of invoice update or webhook configuration updates are non-critical and workaroundable.