How do I install Billium?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Billium need an API key?

The publisher lists these environment variables: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID, BILLIUM_BASE_URL.

What transport does Billium use?

Billium runs locally over stdio.

Billium

by io.github.BilliumHQ

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y @billium/[email protected]

Credentials from the publisher

BILLIUM_API_KEY — Secret API key (sk_...), from the dashboard under Settings → Developer → API keys.
BILLIUM_MERCHANT_ID — Merchant ID (mer_...).
BILLIUM_BASE_URL — Override the API base URL (testing / staging environments).

Provider

Claude Code

BILLIUM_API_KEY=<secret> BILLIUM_MERCHANT_ID=<value> BILLIUM_BASE_URL=<value> claude mcp add io.github.billiumhq-billium -- npx -y @billium/[email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.billiumhq-billium": {
      "command": "npx",
      "args": [
        "-y",
        "@billium/[email protected]"
      ],
      "env": {
        "BILLIUM_API_KEY": "<secret>",
        "BILLIUM_MERCHANT_ID": "<value>",
        "BILLIUM_BASE_URL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Related skills

View all

Questions

How do I install Billium?: Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Billium need an API key?: The publisher lists these environment variables: BILLIUM_API_KEY, BILLIUM_MERCHANT_ID, BILLIUM_BASE_URL.
What transport does Billium use?: Billium runs locally over stdio.
When was Billium last checked?: Last checked 2026-10-16. Official Billium MCP server: manage crypto invoices, payments, and webhooks from any MCP host.

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#version and packages/node/src/version.ts#SDK_VERSION to the new version (CI verifies they match).
Add a section to packages/node/CHANGELOG.md describing 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 publish with provenance.

License

MIT