Billium

io.github.BilliumHQPublished by GitHub account BilliumHQv0.1.3Updated Oct 24, 2026

Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant create and manage Billium crypto invoices, payments, and webhooks from an MCP host.

What you can do
The official Billium MCP server exposes the Billium payments API to an MCP host so the assistant can work with crypto invoices and webhooks. The registry description says it manages crypto invoices, payments, and webhooks; the README describes the sibling Node.js SDK as covering invoice creation, webhook signature verification, and webhook management. The manifest does not list individual tool names.
When to use it
Use it when you take crypto payments through Billium and want an assistant to handle invoice and webhook work inside your MCP host, such as Claude or Cursor, instead of calling the API by hand.
Requirements
Runs locally as an npm package (@billium/mcp) over stdio, so Node.js is needed. Requires a Billium merchant ID (BILLIUM_MERCHANT_ID) and a secret API key (BILLIUM_API_KEY) from the dashboard under Settings, Developer, API keys. BILLIUM_BASE_URL can override the API base URL for testing or staging. Desktop-only; no web executable.
Before you install
The server needs a secret API key (BILLIUM_API_KEY) and a merchant ID, which grant access to a live payments account; keep them out of shared configuration. It can create invoices and manage webhooks, so actions may affect real payment flows and money. The README also references a webhook secret (BILLIUM_WEBHOOK_SECRET) used for signature verification in the SDK.

Installation

In SourceWeft

  1. Open Billium in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Billium SDKs

Official client libraries for Billium — non-custodial crypto payments, invoices, and webhooks.

Packages

PackageVersionDescription
@billium/node[npm]Node.js SDK — invoices, webhook signature verification, webhook management
@billium/mcp[npm]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

bash
npm install @billium/node
typescript
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:

bash
npm install        # installs all workspace packagesnpm run lint       # typechecks every package (src + tests)npm test           # runs every package's test suitenpm 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:

  1. Bump packages/node/package.json#version and packages/node/src/version.ts#SDK_VERSION to the new version (CI verifies they match).
  2. Add a section to packages/node/CHANGELOG.md describing the changes.
  3. Commit the bump on main.
  4. Tag and push: git tag v1.0.1 && git push origin v1.0.1.
  5. The release workflow runs lint, test, build, then npm publish with provenance.

License

MIT

Source: README.md at commit 1ebbb70

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts