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.
Every sibling server's tools arrive as one entry, so mcp.json holds one object with one required type field instead of 31, and the Customize page lists one server to enable or disable. Only four of the 292 names needed a server-name prefix to stay unique: invoice_business_set and docx_business_set, expense-tracker_category_rules and bank-statement_category_rules.
| 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 .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
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.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"office-suite": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/office-suite/dist/index.js"]
}
}
}The 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:
{
"mcpServers": {
"office-suite": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-office-suite"]
}
}
}The Customize page shows the server and its tools once it has started.
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 current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: each child keeps its own free tier. Pro is $39 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Office Suite pasting the config block above is the supported route.
The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor 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