Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Description from the maker (original English)
Unofficial MCP server for Karbon practice management: contacts, work, time, invoices, payments.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
KARBON_BEARER_TOKEN, KARBON_ACCESS_KEY, KARBON_READ_ONLY, KARBON_ALLOW_PAYMENT_WRITESValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"karbon": {
"command": "npx",
"args": [
"-y",
"karbon-mcp-server"
],
"env": {
"KARBON_BEARER_TOKEN": "your-value",
"KARBON_ACCESS_KEY": "your-value",
"KARBON_READ_ONLY": "your-value",
"KARBON_ALLOW_PAYMENT_WRITES": "your-value"
}
}
}
}Run this in your terminal
claude mcp add karbon --env KARBON_BEARER_TOKEN=your-value --env KARBON_ACCESS_KEY=your-value --env KARBON_READ_ONLY=your-value --env KARBON_ALLOW_PAYMENT_WRITES=your-value -- npx -y karbon-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"karbon": {
"command": "npx",
"args": [
"-y",
"karbon-mcp-server"
],
"env": {
"KARBON_BEARER_TOKEN": "your-value",
"KARBON_ACCESS_KEY": "your-value",
"KARBON_READ_ONLY": "your-value",
"KARBON_ALLOW_PAYMENT_WRITES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"karbon": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"karbon-mcp-server"
],
"env": {
"KARBON_BEARER_TOKEN": "your-value",
"KARBON_ACCESS_KEY": "your-value",
"KARBON_READ_ONLY": "your-value",
"KARBON_ALLOW_PAYMENT_WRITES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
KARBON_READ_ONLY envKARBON_ALLOW_PAYMENT_WRITES envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified with the GitHub account Mad-Man-Dan, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: KARBON_BEARER_TOKEN, KARBON_ACCESS_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
🚧 Early release — this project is brand new and we're actively making updates over the next few days. Things may change quickly; pin a version if you need stability, and check back soon.
An unofficial Model Context Protocol server for Karbon practice management. Connect Claude Code, Claude Desktop, GitHub Copilot, or any MCP-compatible client to your Karbon instance and work with contacts, work items, time, invoices, payments, files, and more using natural language.
Disclaimer: This is a community project and is not affiliated with or endorsed by Karbon. Use at your own risk.
| Area | Tools |
|---|---|
| Contacts | list_contacts, get_contact, create_contact, update_contact |
| Organizations | list_organizations, get_organization, create_organization, update_organization |
| Client groups | list_client_groups, get_client_group, create_client_group, update_client_group |
| Work items | list_work_items, get_work_item, get_estimate_summary, create_work_item, update_work_item |
| Notes & comments | get_note, create_note, get_comment |
| Timesheets | list_timesheets, get_timesheet, list_time_entries, get_time_entry (read-only) |
| Invoices | list_invoices, get_invoice (read-only) |
| Payments | list_payments, get_payment; plus create_manual_payment, delete_manual_payment, reverse_manual_payment behind KARBON_ALLOW_PAYMENT_WRITES=true |
| Business cards | get_business_card, update_business_card — contact details (email, phone, address) |
| Custom fields | list_custom_fields, get_custom_field_values, set_custom_field_values, create_custom_field, delete_custom_field |
| Files | list_entity_files, download_file, upload_file |
| Teams | list_teams, get_team, add_team_members, remove_team_member |
| Work schedules | get_work_schedule, create_work_schedule, update_work_schedule |
| Users | list_users, get_user |
| Account | get_tenant_settings, list_work_templates, get_work_template |
get_contact, get_organization, and get_client_group can also look records up by your own UserDefinedIdentifier instead of the Karbon key — handy if you sync IDs from your tax software.
All list tools support OData filtering ($filter), ordering ($orderby), and pagination ($top/$skip) — so you can ask things like *"show my in-progress work items due this month"* and the AI can express that as a precise query.
Step-by-step walkthroughs for Claude Desktop, claude.ai/Cowork, and ChatGPT (written for non-developers) are in docs/client-guides.md.
Download karbon-mcp-server.mcpb from the latest release and double-click it. Claude Desktop opens a form for your two Karbon keys (stored securely by your OS) plus a read-only toggle — no terminal needed. Walkthrough.
No Node.js? These check for it (installing via winget/Homebrew where possible), then run the setup wizard straight from npm — no repo clone, no manual download:
# Windows (PowerShell)
irm https://raw.githubusercontent.com/Mad-Man-Dan/karbon-mcp-server/main/scripts/install.ps1 | iex
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/Mad-Man-Dan/karbon-mcp-server/main/scripts/install.sh | bash
npx -y karbon-mcp-server setup
Setup asks a few quick questions — project or user-level install, your API keys (skippable), and whether to enable read-only mode — then does everything else automatically:
.mcp.json (Claude Code), plus .vscode/mcp.json and .cursor/mcp.json if those folders exist in the project.mcp add CLI).It then offers to take your two Karbon keys (Enter skips either one):
* per character, then a first-4/last-4 preview (like 1a2b****5c6d, the same style Karbon's site uses) so you can confirm what was entered, with a gentle warning if the format looks off (the Bearer Token is a GUID; the Access Key starts with ey...).It backs up every existing config file before touching it, merges rather than overwrites, and never replaces real credentials with placeholders (re-running and skipping the prompts keeps your existing keys). If you go project-level, gitignore the config files — your keys live in them in plain text.
Options:
npx -y karbon-mcp-server setup --scope project # skip the question
npx -y karbon-mcp-server setup --scope user npx -y karbon-mcp-server setup --read-only # disable all write tools npx -y karbon-mcp-server setup --client vscode,cursor # only these clients
npx -y karbon-mcp-server setup --print # just print the JSON
The Install in VS Code / Cursor badges above create the server entry for you with placeholder credentials. After installing, replace YOUR_BEARER_TOKEN and YOUR_ACCESS_KEY with your real keys — in VS Code via the Command Palette → MCP: Open User Configuration, in Cursor by editing ~/.cursor/mcp.json.
If you run the server before replacing the placeholders, it starts fine and every tool responds with setup instructions instead of failing cryptically — so you can even ask your AI assistant "why isn't Karbon working?" and it will tell you what to do.
Prefer to configure things by hand? Each client is below.
claude mcp add karbon \
--env KARBON_BEARER_TOKEN=your-bearer-token \ --env KARBON_ACCESS_KEY=your-access-key \ -- npx -y karbon-mcp-server
Add to claude_desktop_config.json:
{
"mcpServers": { "karbon": { "command": "npx", "args": ["-y", "karbon-mcp-server"], "env": { "KARBON_BEARER_TOKEN": "your-bearer-token", "KARBON_ACCESS_KEY": "your-access-key" } } } }
Add to .vscode/mcp.json in your workspace (or your user mcp.json):
{
"servers": { "karbon": { "command": "npx", "args": ["-y", "karbon-mcp-server"], "env": { "KARBON_BEARER_TOKEN": "your-bearer-token", "KARBON_ACCESS_KEY": "your-access-key" } } } }
Add to ~/.cursor/mcp.json (or use the install badge above):
{
"mcpServers": { "karbon": { "command": "npx", "args": ["-y", "karbon-mcp-server"], "env": { "KARBON_BEARER_TOKEN": "your-bearer-token", "KARBON_ACCESS_KEY": "your-access-key" } } } }
codex mcp add karbon \
--env KARBON_BEARER_TOKEN=your-bearer-token \ --env KARBON_ACCESS_KEY=your-access-key \ -- npx -y karbon-mcp-server
Or add to ~/.codex/config.toml:
[mcp_servers.karbon]
command = "npx" args = ["-y", "karbon-mcp-server"]
[mcp_servers.karbon.env] KARBON_BEARER_TOKEN = "your-bearer-token" KARBON_ACCESS_KEY = "your-access-key"
These clients can't launch local servers — they only connect to a remote MCP server over HTTPS. This package includes a streamable-HTTP mode for exactly that, so a firm can self-host it and keep their Karbon keys in their own infrastructure:
KARBON_BEARER_TOKEN=... KARBON_ACCESS_KEY=... KARBON_HTTP_SECRET=some-long-random-string \
npx -y karbon-mcp-server --http --port 8787
This serves the MCP endpoint at /mcp/ (plus a /health check). Expose it over HTTPS however you like — the quickest free option is a Cloudflare Tunnel:
cloudflared tunnel --url http://localhost:8787
Then add the URL (e.g. https://your-tunnel.trycloudflare.com/mcp/your-secret) as:
Security notes: anyone with the full URL has the same Karbon access as your API keys, so use a long random
KARBON_HTTP_SECRET, always front it with HTTPS, and considerKARBON_READ_ONLY=truefor remote use. There is deliberately no shared/hosted instance of this server — your keys should only ever live on infrastructure you control.
| Environment variable | Required | Description |
|---|---|---|
KARBON_BEARER_TOKEN | Yes | Bearer token from Karbon Connected Apps |
KARBON_ACCESS_KEY | Yes | Access key (JWT) from Karbon Connected Apps |
KARBON_READ_ONLY | No | Set to true to disable all create/update tools |
KARBON_ALLOW_PAYMENT_WRITES | No | Set to true to enable the payment write tools (create/delete/reverse manual payments). Off by default |
KARBON_API_BASE_URL | No | Override the API base URL (default https://api.karbonhq.com/v3) |
KARBON_HTTP_SECRET | No | HTTP mode only: secret path segment for the endpoint (/mcp/ ) |
PORT | No | HTTP mode only: port to listen on (default 8787; --port wins) |
If you want a guarantee that the AI can never modify your Karbon data, set KARBON_READ_ONLY=true (or pass --read-only). Write tools are not registered at all in this mode, so the AI never sees them. This also disables download_file — it doesn't change Karbon, but it writes to the local disk, and read-only means no writes anywhere. The setup wizard asks about this.
Changing it later: setup always writes the toggle explicitly ("KARBON_READ_ONLY": "true" or "false"), so the switch is right there i
Only the beginning is shown; read the rest in the repo