Paymenter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYMENTER_URL | Yes | The base URL of your Paymenter instance API (e.g. https://billing.yourdomain.com/api). | |
| PAYMENTER_API_TOKEN | Yes | Your Paymenter API Bearer token, generated with Administrator privileges inside the Paymenter admin control panel. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paymenter_health_checkA | Check connectivity to Paymenter API and verify administrative API token authentication. |
| paymenter_searchC | Universal search across multiple Paymenter entities (users, orders, services, invoices, tickets) matching a search query. |
| paymenter_get_dashboard_summaryB | Fetch key operational metrics and statistics: total users, active services, pending invoices, open tickets. |
| paymenter_list_usersB | List customer accounts with pagination, sorting, and filtering. |
| paymenter_get_userC | Retrieve detailed profile information for a specific user by ID. |
| paymenter_create_userC | Register and create a new customer account in Paymenter. |
| paymenter_update_userC | Update profile or credentials of an existing user. |
| paymenter_delete_userA | Permanently delete a user account from Paymenter (irreversible). |
| paymenter_get_user_overviewA | Fetch consolidated user overview including active services, open tickets, recent invoices, and credit balance. |
| paymenter_list_ordersB | List customer orders with pagination, sorting, and relations. |
| paymenter_get_orderC | Get order details by order ID. |
| paymenter_create_orderC | Create a new order for a user. |
| paymenter_delete_orderB | Permanently delete an order by ID. |
| paymenter_list_servicesC | List provisioned hosting/digital services. |
| paymenter_get_serviceC | Get detailed service provision record by ID. |
| paymenter_create_serviceC | Provision and assign a new digital/hosting service to a customer. |
| paymenter_update_serviceB | Update properties or metadata of a service. |
| paymenter_suspend_serviceA | Suspend an active service (e.g. for overdue invoice or abuse). |
| paymenter_unsuspend_serviceB | Reactivate a suspended service to active status. |
| paymenter_renew_serviceC | Renew a service by extending its expiration date. |
| paymenter_cancel_serviceC | Cancel a service gracefully. |
| paymenter_list_invoicesC | List invoices with status, user filtering, and pagination. |
| paymenter_get_invoiceB | Get invoice details and line items by invoice ID. |
| paymenter_create_invoiceC | Create a new invoice for a customer. |
| paymenter_update_invoiceC | Update invoice status or due date. |
| paymenter_delete_invoiceB | Permanently delete an invoice record. |
| paymenter_create_invoice_itemC | Add a line item or charge to an existing invoice. |
| paymenter_manage_creditC | Manage user prepaid credits wallet: list, get, deposit, update, or delete balances. |
| paymenter_list_ticketsB | List customer support tickets with filters. |
| paymenter_get_ticketA | Get ticket details and message thread by ticket ID. |
| paymenter_create_ticketC | Open a new customer support ticket. |
| paymenter_reply_ticketB | Post a reply message to an existing support ticket thread. |
| paymenter_list_productsC | List available products/plans in the catalog. |
| paymenter_list_categoriesC | List product categories in Paymenter. |
| paymenter_manage_affiliateC | Manage affiliate partner accounts: list, get, create, update, or delete. |
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 35 tools
Each tool targets a distinct resource and action; search vs. list tools are differentiated by query-based vs. filtered listing, and get_user vs. get_user_overview are clearly separate. No major overlaps or ambiguous pairs.
All tools use the paymenter_ prefix and snake_case, mostly following a verb_noun pattern. Minor deviations: health_check is noun-based, and manage_credit/manage_affiliate bundle multiple actions unlike the per-action tools.
With 35 tools, this exceeds the 25+ threshold for 'too many' under the rubric. While the billing domain is broad, many operations could be consolidated, especially since multi-action tools like manage_credit already exist elsewhere.
Core user, service, invoice, and affiliate/credit lifecycles are well covered. However, notable gaps exist: no ticket close/status update, no order update, and products/categories are read-only, which can block common admin workflows.