Billium
Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@billium/mcpclaude mcp add billium -e 'BILLIUM_API_KEY=<your billium_api_key>' -e 'BILLIUM_MERCHANT_ID=<BILLIUM_MERCHANT_ID>' -e 'BILLIUM_BASE_URL=<BILLIUM_BASE_URL>' -- npx -y @billium/mcp@0.1.3
{
"mcpServers": {
"billium": {
"command": "npx",
"args": [
"-y",
"@billium/mcp@0.1.3"
],
"env": {
"BILLIUM_API_KEY": "<your billium_api_key>",
"BILLIUM_MERCHANT_ID": "<BILLIUM_MERCHANT_ID>",
"BILLIUM_BASE_URL": "<BILLIUM_BASE_URL>"
}
}
}
}
Environment variables
BILLIUM_API_KEYrequired secret Secret API key (sk_...), from the dashboard under Settings → Developer → API keys.BILLIUM_MERCHANT_IDrequired Merchant ID (mer_...).BILLIUM_BASE_URLOverride the API base URL (testing / staging environments).
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Billium SDKs
Official client libraries for Billium — non-custodial crypto payments, invoices, and webhooks.
Packages
| Package | Version | Description |
|---|---|---|
@billium/node | Node.js SDK — invoices, webhook signature verification, webhook management | |
@billium/mcp | MCP server — manage invoices and webhooks from Claude, Cursor, and any MCP host |
Additional language SDKs will live as siblings under packages/ as they ship.
Quick start
npm install @billium/node
import { Billium } from '@billium/node';
const billium = new Billium({
apiKey: process.env.BILLIUM_API_KEY,
merchantId: process.env.BILLIUM_MERCHANT_ID,
webhookSecret: process.env.BILLIUM_WEBHOOK_SECRET,
});
const invoice = await billium.invoices.create(
{ name: 'Order #1234', rawAmount: 99.99 },
{ idempotencyKey: crypto.randomUUID() },
);
See packages/node/README.md for the full Node.js SDK reference.
Repository layout
.
├── packages/
│ ├── node/ # @billium/node — TypeScript Node.js SDK
│ │ ├── src/ # Source
│ │ ├── tests/ # Vitest test suite
│ │ ├── README.md # Public-facing docs (rendered on npmjs.com)
│ │ └── CHANGELOG.md # Per-release notes
│ └── mcp/ # @billium/mcp — Model Context Protocol server
│ ├── src/ # Server + tool definitions
│ ├── tests/ # Vitest in-memory round-trip suite
│ └── README.md # Host setup (Claude Code, Cursor, …)
└── .github/
├── workflows/ # CI + release automation
├── ISSUE_TEMPLATE/ # Bug + feature request forms
└── CODEOWNERS # Review requirements
Development
This is an npm workspace. Run scripts from the repository root:
npm install # installs all workspace packages
npm run lint # typechecks every package (src + tests)
npm test # runs every package's test suite
npm run build # builds every package
To work on a specific package, you can also cd packages/node && npm <script>.
Releasing
Releases are published to npm by GitHub Actions when a v*.*.* tag is pushed:
- Bump
packages/node/package.json#versionandpackages/node/src/version.ts#SDK_VERSIONto the new version (CI verifies they match). - Add a section to
packages/node/CHANGELOG.mddescribing the changes. - Commit the bump on
main. - Tag and push:
git tag v1.0.1 && git push origin v1.0.1. - The release workflow runs lint, test, build, then
npm publishwith provenance.
License
Frequently asked questions
What is Billium?
Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.
How do I install Billium?
It runs on your machine. In Claude Code: claude mcp add billium -e 'BILLIUM_API_KEY=<your billium_api_key>' -e 'BILLIUM_MERCHANT_ID=<BILLIUM_MERCHANT_ID>' -e 'BILLIUM_BASE_URL=<BILLIUM_BASE_URL>' -- npx -y @billium/mcp@0.1.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Billium need an API key?
Yes. It expects BILLIUM_API_KEY, BILLIUM_MERCHANT_ID, which you set in its configuration.
Is Billium open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Billium?
It is published by BilliumHQ. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.