Bukku

Tools for the Bukku accounting platform.

Packages

Related MCP server: invoiceninja-mcp

Quick Start

For AI assistants (MCP)

Connect your AI client to the Bukku API. See the MCP package README for setup instructions.

npx @centry-digital/bukku-mcp

For command line

Manage invoices, contacts, products, and more from your terminal. See the CLI package README for full documentation.

npx @centry-digital/bukku-cli --help

Both packages require a Bukku API token and company subdomain. See Getting Your API Token.

Payment terms on quotes and orders: old vs new format

From 21 October 2026, Bukku's API changelog moved sales quotes and sales orders to a new payment-terms format, term_items, replacing the old top-level term_id. A live test on 22 October 2026 found Bukku still applying the old format, but since 23 October 2026 the daily API monitor has confirmed that Bukku now applies term_items on quotes. Use term_items.

So that payment terms stick whichever format Bukku honours, the CLI and MCP server:

1. Both forms. A single term for 100%, given in either format, is sent as both a top-level term_id and term_items. This keeps older integrations working while Bukku phases term_id out.

2. Retry. If Bukku refuses term_id (a validation error on that field), the request is sent again with term_items only.

3. Check. After a create or update, the stored term_items are compared with the request. If they differ, the result carries a warnings field. Sales invoices are unaffected: they already use term_items. Contacts now need a contact_code on create and update, which the live API enforces.

Uninstalling

Step 1: Remove the MCP server configuration

Remove the "bukku" entry from the "mcpServers" object in your AI client's config file.

Claude Code: Remove from .claude/settings.json in your project directory (or ~/.claude/settings.json if added globally).

Claude Desktop: Remove from your config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

After editing, restart your AI client for the changes to take effect.

Step 2: Remove the package (if installed globally)

If you installed the package globally with npm install -g, uninstall it:

npm uninstall -g @centry-digital/bukku-mcp

If you were using npx (the default Quick Start method), there is no persistent installation to remove — npx downloads the package temporarily each time it runs. You can optionally clear the npx cache:

npx clear-npx-cache

Step 3: Revoke your API token (optional)

If you no longer need API access, log into your Bukku account and revoke the token at Control Panel > Integrations > API Access.

Development

Prerequisites

• Node.js v20 or later

Setup

git clone https://github.com/centry-digital/bukku.git
cd bukku
npm ci
npm run verify

npm run verify runs format, lint, build, typecheck, tests and the MCP/CLI parity check, the same as CI. See CONTRIBUTING.md for how every change is tested and verified, and docs/github-setup.md for the repository settings.

Monorepo Structure

packages/
  core/   Shared API client, entities, and types (internal)
  mcp/    MCP server package (@centry-digital/bukku-mcp)
  cli/    CLI package (@centry-digital/bukku-cli)

Both mcp and cli depend on core, which is bundled at build time and not published separately.

License

MIT