BillingServ MCP Server

What BillingServ MCP Server MCP server does

BillingServ MCP Server MCP server gives AI assistants access to selected BillingServ API v2 operations. It covers customer records, invoices, orders, packages, reports, support tickets, marketing data, usage metering, settings, VPN information, geography, modules, and software licensing.

The server supports both read and write workflows. Assistants can inspect unpaid or historical billing data, review available package changes, query revenue reports, create support tickets, add customer notes, create orders or invoices, manage packages, and activate, validate, or deactivate software licenses.

How it works

The server communicates with an MCP client over stdio and sends requests to the BillingServ API base URL configured in the environment. A compiled endpoint allowlist determines which routes can be called, and that list is checked for every request.

Assistants can first call billingserv_list_endpoints to learn the available routes, descriptions, required parameters, and accepted values. billingserv_get then calls one permitted GET route, using query parameters or path values as required. billingserv_create handles the permitted POST operations and licensing actions.

Read and write actions are exposed separately. This allows a client to permit lookups while placing approval controls around actions that create or modify records. The API key is sent only to the configured base URL and is not returned in tool output. Licensing routes use the submitted license key as required by BillingServ rather than sending the BillingServ bearer token.

Setup and configuration

Node.js 20 or newer and a BillingServ API key are required. The standard launch command is npx -y @billingserv/mcp-server.

Set these variables before starting the server:

• BILLINGSERV_API_BASE_URL: BillingServ API v2 base URL, such as https://billing.example.com/api/v2.
• BILLINGSERV_API_KEY: BillingServ API key.
• BILLINGSERV_TIMEOUT_MS: Optional request timeout in milliseconds; the default is 15000.

The README provides configuration examples for Claude Code, Claude Desktop, OpenAI Codex CLI, Cursor, VS Code with GitHub Copilot, and Gemini CLI. Other MCP clients can use the same stdio command and environment variables.

Tools and capabilities

The three MCP tools are:

• billingserv_list_endpoints: Enumerates callable BillingServ routes and their parameter requirements.
• billingserv_get: Calls an allowlisted API v2 GET endpoint. Path placeholders use a path object; other parameters use query.
• billingserv_create: Calls approved POST routes for creating or updating records, and handles license activation, validation, and deactivation.

Read operations include customer, invoice, order, package, report, ticket, marketing, metering, settings, VPN, geography, and module endpoints. Write operations include ticket creation and replies, order creation, customer creation and notes, invoice and quote creation, invoice sending and reminders, package management, discount creation, and licensing actions.

Package creation and updates can include BillingServ's digital_delivery settings, including download policies, download limits, licensing controls, activation limits, and offline-cache duration.

Limitations and notes

Only endpoints included in the built-in allowlist are callable. Password-reset routes and other non-allowlisted routes are excluded. Deleting records and capturing payments are not available through the server.

The write tool can change BillingServ data, so it should be placed behind client approval when confirmation is required. The server does not provide a general-purpose arbitrary API proxy; requests must match the supported endpoint and parameter structure.

BillingServ MCP Server MCP server depends on a reachable BillingServ API v2 installation, a valid API key, and correct endpoint configuration. Its MIT license applies to the project.