BillingServ MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BILLINGSERV_API_KEY | Yes | Your BillingServ API key | |
| BILLINGSERV_TIMEOUT_MS | No | Request timeout in milliseconds | 15000 |
| BILLINGSERV_API_BASE_URL | Yes | Your BillingServ API v2 base URL, e.g. https://billing.example.com/api/v2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| billingserv_list_endpointsA | List every BillingServ billing API endpoint available through this server, with descriptions and required parameters. Read endpoints cover customers, invoices, payments, orders, packages, discounts, support tickets, usage meters, settings, and sales/revenue reports. Write endpoints cover creating and updating tickets, orders, customers, invoices, quotes, discounts, packages, package groups, and package options, and sending invoices and payment reminders. |
| billingserv_getA | Fetch live billing data from the BillingServ API: customers, invoices (including unpaid and overdue), payment methods, transactions, orders, subscriptions, packages, discounts, usage meters, tax and staff settings, and sales/revenue reports. Use this for any question about billing, invoices, customers, orders, or revenue. Only allowlisted endpoints can be called. |
| billingserv_createA | Create or update records in BillingServ: support tickets and ticket replies, orders, customers, customer notes, invoices, quotes, discounts, packages, package groups, and package options. Can also send an invoice or payment reminder to a customer by email. This tool changes real billing data and can email customers, so confirm the details with the user before calling it. Only allowlisted endpoints can be called; deleting records and capturing payments are not available through this server. |
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 3 tools
Each tool has a clearly distinct purpose: create/update, fetch data, and list endpoints. No overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern: billingserv_create, billingserv_get, billingserv_list_endpoints. Perfectly predictable.
Three tools is well-scoped for a billing API server. Each tool serves a broad but necessary function, and the count feels appropriate for the domain.
The tools cover a wide range of billing operations: create/update many resources, fetch various data, and discover other endpoints. Minor gaps like delete and payment capture exist but are intentionally excluded.