@payre/mcp
OfficialInteract with the Payre Web3 Payment Gateway to manage merchant, business, invoice, transaction, analytics, chain, and webhook operations via MCP.
Retrieve merchant profile, KYC status, tier limits, and active business context.
Create, list, update, delete, and switch business contexts with EVM/Solana payout wallets.
Generate crypto checkout invoices (USDC/USDT) with buyer checkout links.
List, inspect, and cancel invoices, including deposit sessions and on-chain receipts.
List settlement transactions and on-chain receipts.
View merchant volume analytics, earnings, and tier limit usage.
Query supported chains, tokens, and contracts.
Inspect webhook delivery logs and retrieve HMAC signing secret.
Regenerate public and secret API keys.
Access MCP resources (supported chains, profile, stats) and prompt templates (create invoice, check account status).
Supports Polygon blockchain for generating crypto checkout invoices, querying supported tokens, and monitoring settlements and transaction confirmations.
Supports Solana for managing payout destinations, querying supported tokens, and monitoring direct-to-wallet settlements and transaction confirmations.
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., "@@payre/mcp Create a crypto checkout invoice for 0.05 ETH"
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.
@payre/mcp
The official Model Context Protocol (MCP) server for the Payre Web3 Payment Gateway by PAYRE INFRA LTD (payre.io).
This MCP server allows AI assistants (Claude Desktop, Cursor, Antigravity, Zed, OpenCode, etc.) to securely interact with the Payre direct-to-wallet payment infrastructure to:
Generate instant non-custodial stablecoin checkout invoices on Base (USDC, USDT)
Monitor direct-to-wallet settlements and transaction confirmations on Base
Manage business contexts and Base payout destinations
Inspect merchant analytics, volume statistics, and compliance tier limits
Query supported Base network configurations and stablecoin contracts (USDC, USDT)
Inspect webhook delivery logs and signing secrets
Installation
# Global install or run directly with npx
npm install -g @payre/mcpRelated MCP server: Yolfi MCP Server
Configuration
Set the following environment variables in your MCP client configuration or a local .env file:
# Required: Your live merchant Secret API Key (starts with sk_live_...)
PAYRE_SECRET_KEY=sk_live_your_merchant_secret_key_here
# Optional: Payre server URL (defaults to https://payre.onrender.com)
PAYRE_BASE_URL=https://payre.onrender.comMCP Client Setup
1. Claude Desktop (claude_desktop_config.json)
On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"payre": {
"command": "npx",
"args": ["-y", "@payre/mcp"],
"env": {
"PAYRE_SECRET_KEY": "sk_live_your_secret_key_here",
"PAYRE_BASE_URL": "https://payre.onrender.com"
}
}
}
}Or when running locally from this repository:
{
"mcpServers": {
"payre": {
"command": "node",
"args": ["c:/Users/DELL/Projects/payre/payre-mcp/index.js"],
"env": {
"PAYRE_SECRET_KEY": "sk_live_your_secret_key_here",
"PAYRE_BASE_URL": "http://localhost:3000"
}
}
}
}2. Cursor IDE (.cursor/mcp.json)
{
"mcpServers": {
"payre": {
"command": "npx",
"args": ["-y", "@payre/mcp"],
"env": {
"PAYRE_SECRET_KEY": "sk_live_your_secret_key_here"
}
}
}
}Available Tools
Tool Name | Description |
| Retrieve authenticated merchant details, KYC status, and compliance tier limits. |
| List all business contexts with EVM & Solana payout wallets and domain verification status. |
| Get full details of a specific business context by UUID. |
| Retrieve the currently active business context. |
| Create a new business context with friendly name and payout wallet addresses. |
| Update an existing business name, payout wallets, or domain. |
| Delete a business context by UUID. |
| Change the default active business context for invoice generation. |
| Generate a direct-to-wallet crypto checkout invoice and buyer checkout link. |
| List invoices with status, amounts, and pagination. |
| Deep inspection of an invoice, including active deposit sessions and on-chain tx receipts. |
| Retrieve settlement transaction records and on-chain receipts. |
| Retrieve merchant volume analytics, earnings, and rolling tier limit usage. |
| Retrieve active EVM and Solana blockchains and supported token contracts. |
| Inspect webhook delivery history and HTTP response statuses. |
| Retrieve merchant's HMAC webhook signing secret. |
| Regenerate public ( |
MCP Resources
payre://docs/supported-chains: Supported blockchains, tokens, and settlement times.payre://merchant/profile: Merchant account verification tier and profile data.payre://merchant/stats: Performance and revenue metrics.
MCP Prompt Templates
create-crypto-invoice: Interactive prompt to assist in generating a payment invoice for a customer.check-account-status: Prompt to review merchant account health, balance, and recent transaction log.
License
MIT © PAYRE INFRA LTD
Available Tools
18 toolscreate_businessB
Create a new business context for receiving direct crypto payments.
Inputs: business_name (required), wallet_address, solana_wallet_address.
create_invoiceA
Create a new payment checkout invoice and generate the buyer checkout URL.
Inputs: amount_usd (required), currency, cancel_url, business_id, +4 more.
delete_businessB
Delete a business context by UUID.
Inputs: business_id (required).
delete_invoiceC
Cancel or delete an invoice by UUID.
Inputs: invoice_id (required).
get_active_businessA
Retrieve the currently active business context used as default for invoice generation.
Inputs: no named parameters.
get_businessB
Get full details of a specific business context by UUID.
Inputs: business_id (required).
get_invoice_detailsA
Get full details of a specific invoice including active payment deposit sessions and payment transactions.
Inputs: invoice_id (required).
get_merchant_statsA
Retrieve volume analytics, invoice counts (paid/pending/expired), net revenue, and compliance tier limits usage.
Inputs: no named parameters.
get_profileA
Get details of the currently authenticated merchant profile, including tier, KYC status, compliance limits, and active business context.
Inputs: no named parameters.
get_webhook_deliveriesB
Fetch webhook delivery attempt logs for a specific invoice.
Inputs: invoice_id (required), limit, offset.
get_webhook_secretA
Retrieve merchant webhook HMAC signing secret used for verifying webhook callbacks.
Inputs: no named parameters.
list_businessesA
List all business contexts configured under the merchant account with their payout wallet addresses and domain verification status.
Inputs: no named parameters.
list_chainsA
Retrieve configured EVM and Solana chains and their active payment currencies/tokens.
Inputs: include_inactive.
list_invoicesA
List invoices created by this merchant, with pagination.
Inputs: limit, offset, business_id.
list_transactionsB
List payment transaction records and ledger settlements associated with the merchant account.
Inputs: limit, offset.
regenerate_api_keysA
Regenerate public (pk_live_...) and secret (sk_live_...) API keys for the merchant account.
Inputs: no named parameters.
switch_active_businessC
Switch the active business context (used as default for checkout invoice generation).
Inputs: business_id (required).
update_businessB
Update an existing business context name, payout wallets, or domain.
Inputs: business_id (required), domain, business_name, wallet_address, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.
Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.
Crypto payments for AI agents: self-serve account, invoices, receiving, payouts, exchange.
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceConnects the Payoza crypto payments API to AI assistants, enabling users to manage transactions, subscriptions, and payment links across multiple blockchains. It provides a comprehensive suite of tools for handling checkout sessions, customers, and real-time revenue analytics through natural language commands.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to set up crypto checkout integration by registering workspaces, creating paylinks and public payment invoices, configuring webhook endpoints, verifying webhook signatures, and checking stablecoin payment status.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to add stablecoin checkout, create payment links and invoices, configure webhooks, verify payment signatures, and gate access based on confirmed payment events.MIT
- AlicenseBqualityCmaintenanceEnables an AI coding assistant to create and manage products, prices, payment links, invoices, customers, subscriptions, entitlements, refunds, and webhooks, simulate test payments, read payments and receipts, and verify buyer access through a crypto payment API.38105 npmMIT