InvoiceyDocs
Connect & automate

Claude Code

Connect Claude Code to Invoicey’s hosted MCP tools.

Claude Code connects to MCP servers from the CLI, so the same tools available in Cursor work here.

Adding the server

claude mcp add --transport http --scope user invoicey \
  https://invoicey.app/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Verify:

claude mcp list

Prefer user scope

--scope project writes to .mcp.json in the repository, which is checked in and shared. A bearer token does not belong there. User scope keeps it in your own config.

Using it

Tools appear as invoicey tools in any session:

Check my connected workspace and issuer, then look up NFCtron in ARES and prepare a draft for 32 hours of consulting at 1,800 CZK per hour, due in 14 days. Ask for missing dates, VAT and document language. Show the draft before issuing.

And for follow-ups:

List unpaid invoices and tell me which are overdue.

Mark 20260012 as paid and email the client a copy with the ISDOC attached.

Review the invoice and explicitly confirm issuing, sending or recording payment. Host approval controls may vary; the connected workspace permissions still apply.

Workspace issuer first

Add your business in Invoicey and choose its default issuer before drafting. The connected tools load the seller server-side and do not accept issuer or template preset IDs on create_invoice. If the workspace has no usable issuer, drafting fails with setup guidance. See issuer setup.

Troubleshooting