Home · Setup · Claude Desktop

MCP Office Suite in Claude Desktop

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 entry in claude_desktop_config.json instead of 31, which matters more here than anywhere else: this is the client where each extra server is another absolute path to get right, and a six-prompt audit at 186 tools put all 20 tool calls in the correct child, zero wrong-server picks.

What you get in Claude Desktop

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.

Install it in Claude Desktop

The file is claude_desktop_config.json, and the key inside it is mcpServers.

Scope	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

One click, with no JSON. Download office-suite.mcpb from the bundle catalog and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

{
  "mcpServers": {
    "office-suite": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/office-suite/dist/index.js"]
    }
  }
}

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

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-suite

That 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"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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.

Local stdio connection

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.

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

Free: each child keeps its own free tier. Pro is $39 once, verified offline.

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Office Suite does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs · Buy Pro

Related guides & tools

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