Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PAYPING_TOKENYesAPI token from the PayPing panel.
PAYPING_MCP_PROXYNoHTTP 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

Full detail of one payment by its payment code: amount, dates, payer, card, fees, refund state and paymentStatus with a plain-English status_text. Use it to check whether a payment really succeeded.

payping_list_withdrawalsA

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_customerB

One customer by code: name, contact details, address, national id, memo.

payping_list_productsA

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_invoicesC

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_invoiceB

One invoice by code with its items, customer, status and payment code, plus url, the public page where the customer pays.

payping_create_customerB

Save a new customer in the PayPing account and return it with its code (needed for invoices). Creates real data: confirm the details with the user before calling.

payping_create_productA

Create a product (financial item) and return its code. Then payping_create_payment_link makes a public payment page for it. Creates real data: confirm title and price with the user before calling.

payping_create_payment_linkA

Make a permanent public payment page for a product and return its url (https://ppng.ir/d/...), which anyone can open and pay. Creates real data: confirm with the user before calling.

payping_create_couponA

Create an active discount coupon and return its code. Creates real data: confirm with the user first.

payping_create_invoiceA

Create an invoice for a saved customer, ready to pay, and return its code, payCode and url (the public page where the customer pays). It is not sent; use payping_send_invoice or share the url. Creates real data: confirm customer, items and prices with the user before calling.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 21 tools

Disambiguation5/5

Each tool maps to a distinct action+resource: get vs list is consistently signalled by singular/plural names, and create/send operations are clearly separated. Descriptions explicitly clarify overlaps, such as list_transactions vs get_payment, so an agent can select the right tool without ambiguity.

Naming Consistency5/5

All tool names use the same payping_ prefix and snake_case verb_noun pattern. Verbs are predictable (get, list, create, send) and resource names are consistent across pairs.

Tool Count4/5

21 tools is on the heavy side for a single MCP server, but each maps to a distinct PayPing resource or action such as customers, products, coupons, invoices, payments, and withdrawals. The surface is broad rather than redundant, so it remains reasonable though somewhat large.

Completeness3/5

The set covers list/get for most resources and create/send for key workflows, including invoices, payment links, customers, products, and coupons. However, it lacks update/delete operations for mutable resources and has no refund or invoice-cancel tools, which are notable lifecycle gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues