Skip to main content
Glama

@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/mcp

Related 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.com

MCP 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

get_profile

Retrieve authenticated merchant details, KYC status, and compliance tier limits.

list_businesses

List all business contexts with EVM & Solana payout wallets and domain verification status.

get_business

Get full details of a specific business context by UUID.

get_active_business

Retrieve the currently active business context.

create_business

Create a new business context with friendly name and payout wallet addresses.

update_business

Update an existing business name, payout wallets, or domain.

delete_business

Delete a business context by UUID.

switch_active_business

Change the default active business context for invoice generation.

create_invoice

Generate a direct-to-wallet crypto checkout invoice and buyer checkout link.

list_invoices

List invoices with status, amounts, and pagination.

get_invoice_details

Deep inspection of an invoice, including active deposit sessions and on-chain tx receipts.

list_transactions

Retrieve settlement transaction records and on-chain receipts.

get_merchant_stats

Retrieve merchant volume analytics, earnings, and rolling tier limit usage.

list_chains

Retrieve active EVM and Solana blockchains and supported token contracts.

get_webhook_deliveries

Inspect webhook delivery history and HTTP response statuses.

get_webhook_secret

Retrieve merchant's HMAC webhook signing secret.

regenerate_api_keys

Regenerate public (pk_live_...) and secret (sk_live_...) API keys.


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 tools
create_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

    A3.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects 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.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      38
      105 npm
      MIT