payping-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYPING_TOKEN | Yes | API token from the PayPing panel. | |
| PAYPING_MCP_PROXY | No | HTTP proxy URL for every request, e.g. http://user:pass@host:port. System proxy settings are ignored. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| payping_get_profileA | Show the PayPing account behind PAYPING_TOKEN: username, name, email, phone and verification flags. Use first to confirm the token works. |
| payping_get_balanceA | Current PayPing wallet balance in Toman (money received and not yet withdrawn). |
| payping_get_sales_summaryA | Sales totals for a period: total amount (Toman), transaction count and daily averages. Defaults to the last 30 days. |
| payping_list_transactionsA | List payments (newest first) with amount (Toman), payer, description, isPaid and payment code, plus the total count for the same filter. Use payping_get_payment with a code for full detail. |
| payping_get_paymentA | One payment by payment code: amount, dates, payer, card, fees, refund state, paymentStatus plus status_text. Use it to check whether a payment really succeeded. |
| payping_list_withdrawalsB | List settlements (withdrawals to your bank account): date, amount (Toman), code and whether it was paid out, plus the total count. |
| payping_get_withdrawalA | Detail of one settlement by code: amount (Toman), request and payout dates, IBAN, bank tracking number. |
| payping_list_customersB | List saved customers (code, name, phone, email, business name) with the total count. |
| payping_get_customerA | One customer by code: name, contact details, address, national id, memo. |
| payping_list_productsB | List products (PayPing "financial items"): code, title, price (Toman), stock, active, has a payment link. |
| payping_get_productB | One product by code: title, description, price (Toman), stock, tax, image, category. |
| payping_list_couponsB | List discount coupons: name, type (0 = percent, 1 = Toman), amount, code, active, products it applies to. |
| payping_get_couponB | One coupon by code: amount, expiry, max uses, number of buyers and their total spend. |
| payping_list_invoicesB | List invoices: code, number, title, status (0 draft, 1 awaiting payment, 2 paid, 3 overdue, 4 cancelled), total (Toman), due and paid dates, customer. |
| payping_get_invoiceA | One invoice by code with its items, customer, status and payment code, plus |
| payping_create_customerA | Save a new customer in the PayPing account and return it with its |
| payping_create_productA | Create a product (financial item) and return its |
| payping_create_payment_linkA | Make a permanent public payment page for a product; returns its |
| payping_create_couponA | Create an active discount coupon and return its |
| payping_create_invoiceA | Create an invoice for a saved customer; returns |
| payping_send_invoiceA | Send an invoice to its customer by SMS/email from PayPing. Messages a real person: confirm with the user before calling. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a distinct resource+action pair (get_payment vs list_transactions, get_withdrawal vs list_withdrawals, list_coupons vs get_coupon), and entity types (payment, customer, product, coupon, invoice, withdrawal) are clearly separated. Descriptions reinforce boundaries so an agent can reliably pick the right tool.
Every tool uses the payping_ prefix followed by a consistent verb_noun pattern (get_, list_, create_, send_). No camelCase mixing or divergent verb styles; the convention is fully predictable.
21 tools is on the heavier side, but the domain legitimately spans payments, customers, products, coupons, invoices, withdrawals, profile and sales, each with reads and creates. It is slightly wide but each tool earns its place.
Read coverage is thorough (list+get for every entity) and creation is covered, but there are no update or delete operations for customers, products, coupons or invoices, and no refund/payment-charge tool. These are notable gaps that leave several lifecycle operations as dead ends.