Billium runs on your own machine — the client starts it, so there is no endpoint to ping. 54 installs a week from npm. Last commit 22 Jun 2026.
Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.
Today is the operative word: we check Billium every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add billium -e 'BILLIUM_API_KEY=<BILLIUM_API_KEY>' -e 'BILLIUM_MERCHANT_ID=<BILLIUM_MERCHANT_ID>' -- npx -y @billium/mcp
{
"mcpServers": {
"billium": {
"command": "npx",
"args": [
"-y",
"@billium/mcp"
],
"env": {
"BILLIUM_API_KEY": "<BILLIUM_API_KEY>",
"BILLIUM_MERCHANT_ID": "<BILLIUM_MERCHANT_ID>"
}
}
}
}
[mcp_servers.billium]
command = "npx"
args = ["-y", "@billium/mcp"]
env = { BILLIUM_API_KEY = "<BILLIUM_API_KEY>", BILLIUM_MERCHANT_ID = "<BILLIUM_MERCHANT_ID>" }
{
"mcpServers": {
"billium": {
"command": "npx",
"args": [
"-y",
"@billium/mcp"
],
"env": {
"BILLIUM_API_KEY": "<BILLIUM_API_KEY>",
"BILLIUM_MERCHANT_ID": "<BILLIUM_MERCHANT_ID>"
}
}
}
}
{
"servers": {
"billium": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@billium/mcp"
],
"env": {
"BILLIUM_API_KEY": "<BILLIUM_API_KEY>",
"BILLIUM_MERCHANT_ID": "<BILLIUM_MERCHANT_ID>"
}
}
}
}
Put your own values in place of
<BILLIUM_API_KEY> (Secret API key (sk_...), from the dashboard under Settings → Developer → API keys), <BILLIUM_MERCHANT_ID> (Merchant ID (mer_...)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BILLIUM_BASE_URL (Override the API base URL (testing / staging environments)).
21 tools for AI agents to manage BTCPay Server: invoices, payments, stores, webhooks, Lightning
Unofficial MCP server for Karbon practice management: contacts, work, time, invoices, payments.
Official HitPay MCP: sales, payouts, balances; create payment links and invoices. OAuth; no refunds.
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
Non-custodial crypto payments: checkout sessions, invoices, webhooks and test payments. No KYC.
Create invoices and customers and record payments in BillingEngine from any MCP client.
Official Timbrix MCP server: stamp, cancel, and query Mexican CFDI 4.0 invoices from AI agents.
Answers built from our own checks of this server.