mcpField
B
Billium

Billium

Local
billium.toFinance0Updated 19w ago
RepositoryVisit website

About Billium

Billium provides a non-custodial crypto payment SDK and an MCP server for merchants managing invoices and webhooks. Its MCP package makes those management tasks available from Claude, Cursor, and other MCP hosts.

Key features

  1. 01Manage crypto invoices
  2. 02Manage webhooks
  3. 03Verify webhook signatures
  4. 04Node.js SDK for Billium

Use cases

  1. 01Create and manage payment invoices
  2. 02Manage merchant webhooks
  3. 03Verify incoming webhook signatures

MCP support

The @billium/mcp server lets MCP clients manage Billium invoices and webhooks.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "billiumhq-billium": {
      "command": "npx",
      "args": [
        "-y",
        "@billium/mcp"
      ],
      "env": {
        "BILLIUM_API_KEY": "<BILLIUM_API_KEY>",
        "BILLIUM_MERCHANT_ID": "<BILLIUM_MERCHANT_ID>",
        "BILLIUM_BASE_URL": "<BILLIUM_BASE_URL>"
      }
    }
  }
}
Run commandnpx -y @billium/mcp
Environment variables to set
BILLIUM_API_KEYSecretSecret API key (sk_...), from the dashboard under Settings → Developer → API keys.
BILLIUM_MERCHANT_IDMerchant ID (mer_...).
BILLIUM_BASE_URLOverride the API base URL (testing / staging environments).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@billium/mcp0.1.3

Tools

23

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
namestringYesInvoice display name, e.g. "Order #1234".
currencystringNoCurrency code, e.g. 'USD'. Defaults to USD.
rawAmountnumberYesAmount in the given currency (e.g. 99.99).
descriptionstringNo
redirectUrlstringNoURL to send the customer to after a successful payment.
customerNamestringNo
customerEmailstringNo
idempotencyKeystringNoOptional dedup key. If omitted, a UUID is generated so retries never create duplicate invoices.
customerAddressstringNo
customerPhoneNumberstringNo

Details

From the project README

Billium SDKs

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

Packages

PackageVersionDescription
@billium/nodenpmNode.js SDK — invoices, webhook signature verification, webhook management
@billium/mcpnpmMCP 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:

  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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.