Server data from the Official MCP Registry
MCP server for BillingServ: customers, invoices, orders, packages, and revenue reports.
MCP server for BillingServ: customers, invoices, orders, packages, and revenue reports.
The BillingServ MCP server is well-designed with strong security fundamentals. It implements a strict endpoint allowlist, proper environment-based credential handling, and comprehensive input validation. Authentication is required and appropriately scoped. Code quality is high with good error handling and no evidence of malicious patterns. Minor observations around error message verbosity and timeout configuration do not significantly impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: BILLINGSERV_API_BASE_URL
Environment variable: BILLINGSERV_API_KEY
Environment variable: BILLINGSERV_TIMEOUT_MS
Add this to your MCP configuration file:
{
"mcpServers": {
"com-billingserv-mcp": {
"env": {
"BILLINGSERV_API_KEY": "your-billingserv-api-key-here",
"BILLINGSERV_TIMEOUT_MS": "your-billingserv-timeout-ms-here",
"BILLINGSERV_API_BASE_URL": "your-billingserv-api-base-url-here"
},
"args": [
"-y",
"@billingserv/mcp-server"
],
"command": "npx"
}
}
}From the project's GitHub README.
Connect AI assistants like Claude, ChatGPT (Codex), Cursor, and Gemini to your BillingServ account.
This is an MCP server for the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, and reports straight from your BillingServ installation. Ask things like:
And your assistant answers from live billing data instead of guessing.
Safe by design. The server only calls a fixed allowlist of BillingServ endpoints, checked on every request. Today that covers lookups and reports, with support for creating and updating records on the roadmap.
npx comes with it)Every client setup below uses the same three environment variables:
| Variable | Required | Description |
|---|---|---|
BILLINGSERV_API_BASE_URL | Yes | Your BillingServ API v2 base URL, e.g. https://billing.example.com/api/v2 |
BILLINGSERV_API_KEY | Yes | Your BillingServ API key |
BILLINGSERV_TIMEOUT_MS | No | Request timeout in milliseconds (default 15000) |
Find your client below, drop in your URL and API key, and you're done.
One command:
claude mcp add billingserv \
--env BILLINGSERV_API_BASE_URL="https://billing.example.com/api/v2" \
--env BILLINGSERV_API_KEY="your_api_key" \
-- npx -y @billingserv/mcp-server
Restart Claude Code and try asking it to list your BillingServ endpoints.
Open Settings → Developer → Edit Config and add this to claude_desktop_config.json:
{
"mcpServers": {
"billingserv": {
"command": "npx",
"args": ["-y", "@billingserv/mcp-server"],
"env": {
"BILLINGSERV_API_BASE_URL": "https://billing.example.com/api/v2",
"BILLINGSERV_API_KEY": "your_api_key"
}
}
}
}
Restart Claude Desktop and look for the billingserv tools under the tools icon.
Add this to ~/.codex/config.toml:
[mcp_servers.billingserv]
command = "npx"
args = ["-y", "@billingserv/mcp-server"]
[mcp_servers.billingserv.env]
BILLINGSERV_API_BASE_URL = "https://billing.example.com/api/v2"
BILLINGSERV_API_KEY = "your_api_key"
Add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:
{
"mcpServers": {
"billingserv": {
"command": "npx",
"args": ["-y", "@billingserv/mcp-server"],
"env": {
"BILLINGSERV_API_BASE_URL": "https://billing.example.com/api/v2",
"BILLINGSERV_API_KEY": "your_api_key"
}
}
}
}
Add this to .vscode/mcp.json in your workspace:
{
"servers": {
"billingserv": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@billingserv/mcp-server"],
"env": {
"BILLINGSERV_API_BASE_URL": "https://billing.example.com/api/v2",
"BILLINGSERV_API_KEY": "your_api_key"
}
}
}
}
Add this to ~/.gemini/settings.json:
{
"mcpServers": {
"billingserv": {
"command": "npx",
"args": ["-y", "@billingserv/mcp-server"],
"env": {
"BILLINGSERV_API_BASE_URL": "https://billing.example.com/api/v2",
"BILLINGSERV_API_KEY": "your_api_key"
}
}
}
}
Any MCP client that supports stdio servers will work. Point it at:
npx-y @billingserv/mcp-serverThe server gives your assistant two tools:
billingserv_list_endpointsLists 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_getCalls one allowlisted BillingServ API v2 GET endpoint.
{
"endpoint": "customer/get",
"query": { "id": 123 }
}
Endpoints with placeholders in the path take a path object instead:
{
"endpoint": "meter/{customer_id}/get/{order_id}",
"path": { "customer_id": 123, "order_id": 456 }
}
| Area | Endpoints |
|---|---|
| Customers | customer/lists, customer/get, customer/get-credit |
| Invoices | invoice/lists, invoice/get-payment-method, invoice/get-transactions |
| Orders | order/get-orders, order/get-orders-by-status, order/available-package-changes, order/preview-package-change, order/check-fraud |
| Packages | package/lists, package/get, package/show, package/get-by-customer, package/group/lists, package/group/get, package/option/lists, package/option/get |
| Reports | report/annual-sales, report/revenue-trend, report/sales-by-staff, report/sales-by-customer, report/package-leaderboard, report/customer-receipt, report/customer-credit, report/customer-invoice, report/customer-debt, report/login-history |
| Marketing | marketing/lists, marketing/get-discount |
| Usage metering | meter/{customer_id}/get/{order_id} |
| Settings | setting/invoice, setting/lists-staff, setting/get-staff, setting/lists-tax-zone, setting/get-tax-zone, setting/lists-tax-class, setting/get-tax-class |
| VPN | vpn/branding/get, vpn/servers/list |
| Geography | country/lists, country/get, county/lists-by-country |
| Modules | module/get-module-configuration |
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.
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.