PayPing

What the PayPing MCP server does

The PayPing MCP server exposes an Iranian PayPing merchant account to MCP-compatible AI clients. It can retrieve account profile details, wallet balance, sales summaries, transactions, payment status, bank settlements, customers, products, discount coupons, and invoices. List operations support searching or filtering where PayPing provides those options, including invoice filters by status or customer.

The server also supports selected account changes. Agents can save customers, create products with fixed or payer-selected prices, generate product payment links, create discount coupons, create invoices for saved customers, and ask PayPing to send invoices by SMS or email. A typical invoice flow is to create or find a customer, create an invoice, and optionally send it. A product flow can create a product and then return a public payment page.

This belongs in the Finance & Fintech category for workflows that combine an agent with a merchant account. It is not a general payment-processing or payout interface: it cannot withdraw funds, refund or reverse payments, or delete records.

How it works

The PayPing MCP server runs on the user’s machine as a standard stdio process and communicates with PayPing. Authentication uses a PayPing API token supplied through the environment. The token’s scopes control which read and write operations succeed, so a read-only token can be used when the agent should not change account data.

The server exposes 21 tools with the payping_ prefix. Read tools return compact JSON. List responses contain no more than 50 items and include a total, so callers may need to apply search or date filters. Amounts are expressed in Toman, and dates use UTC.

Create and send operations should be confirmed with the user before execution. The server does not itself provide tools for taking raw payments, making payouts, or reversing payment activity.

Setup and configuration

Install with uvx payping-mcp, provided uv and Python 3.10 or newer are available. Installing the package with pip install payping-mcp is another supported option. The required environment variable is PAYPING_TOKEN; PAYPING_MCP_PROXY can optionally specify an HTTP proxy.

Before connecting the server, create a token in the PayPing merchant dashboard and wait for approval. PayPing requires a complete merchant profile for token approval, and newly approved tokens may take about ten minutes to become usable. The token is shown only once when created. Configure only the scopes needed for the intended workflow, such as payment reads, customer access, product access, coupon access, or invoice access.

Claude Desktop, Claude Code, Cursor, and VS Code can use the stdio configuration. Other MCP clients can run the same command with the token in their environment.

Tools and capabilities

• Read profile, balance, sales summaries, transactions, payment details, and withdrawals.
• Search or retrieve customers, products, coupons, and invoices.
• Create customers, products, payment links, coupons, and invoices.
• Send an invoice through PayPing by SMS or email.
• Pass returned customer, product, and invoice codes between related operations.

Limitations and notes

Dashboard-based balance and sales-summary endpoints may reject API tokens even when other tools work. Token scopes can also cause individual tools to return authorization errors. A token with write scopes is needed for creation and invoice-sending operations; omitting those scopes leaves the account unchanged by this server.

The PayPing MCP server acts on the authenticated user’s own account. It does not provide deletion, withdrawal, refund, reversal, or raw payment-collection tools. Keep the token private and use the narrowest practical scope set.