Home · Setup · Claude Code
One config entry that exposes every tool of all 41 sibling servers. It starts all 41 sibling servers as child processes and exposes every tool, resource and prompt under one server, with one license pair. Six of the 380 tool names collided and needed a server-name prefix: business_set from invoice and docx, category_rules from expense-tracker and bank-statement, and asset_add, trip_list and rate_set each from two of asset-register, per-diem, catalogue, maintenance-log and mileage-log.
One `claude mcp add` instead of 31, and one bundle key. The audited round that asked for a logo resize, an invoice PDF and a PAID stamp in one sentence, three children at once, called the right tool in the right child every time.
| You say | Tool |
|---|---|
| Log 3 hours today on Nova design and invoice them at EUR 90. | entry_add then invoice_from_hours |
| Resize this logo to 512px and put it on a PAID stamp on invoice INV-2026-0001's PDF. | image_resize, invoice_pdf, pdf_stamp: three children |
| Zip this month's invoices and quotes. | zip_bundle_month, one call |
A six-prompt audit needing two or more children per sentence put 186 tools on one allowlist, the CLI's own file and web tools denied. Result: 20 of 20 tool calls landed in the correct child and the correct tool, zero wrong-server picks, 13 of 18 scored, against 50 of 51 correct at 108 tools when this bundle held five children.
The file is .mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| local (default) | ~/.claude.json, this project only |
| project | .mcp.json at the repository root |
| user | ~/.claude.json, every project |
If you also run Claude Desktop, the shortest path there is one click: office-suite.mcpb
from the bundle catalog opens as an extension, with no JSON and no terminal.
Claude Code reads its own config, so here it is:
From the terminal, against a built file:
claude mcp add --scope user office-suite -- node /absolute/path/to/mcp-servers/servers/office-suite/dist/index.js
claude mcp list # health-check it before the first prompt
# or --scope project, committed to .mcp.json for the teamThe node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/office-suiteThat writes servers/office-suite/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
claude mcp add office-suite -- npx -y @theluckystrike/mcp-office-suiteNo restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build.
The suite starts 31 child processes, so it has no hosted form of its own. Thirty of those 31 are served individually at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP instead, one connection each: https://mcp.zovo.one/mcp/connect mints a free token and prints a ready URL per server, or use a Pro key as the bearer.
The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.
Free: each child keeps its own free tier. Pro is $39 once, verified offline.
Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.
Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.
This server runs locally over stdio. Use the downloaded local extension in Claude Desktop or build its source and point the client at the absolute dist/index.js path. No hosted endpoint is provided for this server.
The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro
One install, every server: the office-suite bundle · Best MCP servers for small business accounting and paperwork in 2026 · MCP servers for small business accounting: the roundup · How much do MCP servers cost? One-time licenses vs monthly subscriptions