The BillingServ MCP server connects AI assistants like Claude, ChatGPT (Codex), Cursor, and Gemini to your BillingServ account.
It provides Model Context Protocol (MCP) access to the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, software licenses, and reports straight from your BillingServ installation. Ask things like:
BillingServ MCP server for customers, invoices, orders, packages, licenses, and revenue reports.
"Which customers have unpaid invoices this month?"
"Show me the revenue trend for this year."
"What packages does customer 123 have, and what could they upgrade to?"
"Validate this software license activation."
And your assistant answers from live billing data instead of guessing.
You can also ask it to do things: raise a support ticket, create an order, draft an invoice, or add a note to a customer.
Safe by design. The server only calls a fixed allowlist of BillingServ endpoints, checked on every request. Reads and writes are separate tools, so you can let your AI look things up freely while requiring approval for anything that creates or changes records. Deleting records and capturing payments are deliberately not available.
Lists every BillingServ endpoint the server can call, along with descriptions, required parameters, and valid values. Assistants usually call this first to see what data is available.
billingserv_get
Calls one allowlisted BillingServ API v2 GET endpoint.
Creates or updates records through an allowlisted set of POST endpoints. It also activates, validates, and deactivates software licenses. This is the tool to gate behind approval in your MCP client if you want a confirmation step before anything changes.
{
"endpoint": "ticket/create",
"body": {
"subject": "Question about my last invoice",
"user_id": 123,
"message": "Customer called about a duplicate charge.",
"support_department": "billing"
}
}
The endpoint allowlist is compiled into the server and checked on every request. Only allowlisted endpoints can be called.
Sensitive routes like password reset are deliberately left out.
Your API key is read from the environment and only ever sent to the base URL you configure. It's never logged or included in tool output.
Licensing endpoints use the submitted license key as their credential, as required by the API, so the BillingServ bearer token is not sent to those routes.
Development
git clone https://github.com/billingserv/billingserv-mcp-server.git
cd billingserv-mcp-server
npm install
npm run build
BILLINGSERV_API_BASE_URL="https://billing.example.com/api/v2" \
BILLINGSERV_API_KEY="your_api_key" \
npm start
Or put the variables in a local .env file (gitignored) and run npm run start:dev.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Billingserv?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Billingserv einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: BILLINGSERV_API_BASE_URL, BILLINGSERV_API_KEY, BILLINGSERV_TIMEOUT_MS.
Welchen Transport verwendet Billingserv?
Billingserv läuft lokal über stdio.
Wann wurde Billingserv zuletzt geprüft?
Zuletzt geprüft: 2026-11-08. BillingServ MCP server for customers, invoices, orders, packages, licenses, and revenue reports.