InvoiceCave in Claude Code
One CLI command. 102 tools. Manage invoices, customers, payments, and accounting from your terminal — no context switching, no browser.
Generate an API key
Sign in to InvoiceCave → Settings → Security → Generate API Key. Name it "Claude Code". Copy the ic_… value.
Add the MCP server
Run this in any terminal — works inside or outside a Claude Code session:
claude mcp add invoicecave --transport http \ https://www.invoicecave.com/api/mcp/mcp \ --header "Authorization: Bearer ic_your_api_key"
By default this saves to your local .claude/settings.local.json. Add --scope user to make it available across all your projects.
Verify
claude mcp list # Expected output: # invoicecave ✓ Connected (102 tools)
If you see ✗ Failed to connect, double-check your API key — copy/paste sometimes adds whitespace.
Use it
In any Claude Code session, prompts that mention invoicing now flow through 102 real tools instead of guessing:
Claude Code will call create_invoice with the right params. The result appears inline.
Power-user moves
Project-scoped configs
Drop .claude/settings.local.json into any project repo to wire InvoiceCave per-project (e.g., a billing repo where you keep client templates).
Multi-org workflows
Generate a separate API key per InvoiceCave organization and add each as a uniquely-named MCP server (invoicecave-acme, invoicecave-globex). Claude can switch between them in one prompt.
CI/CD invoicing
Use the same API key with our REST API in CI to auto-generate invoices on milestone tags, then have Claude Code review them locally.