Home · Setup · Claude Desktop

MCP Office Suite in Claude Desktop

One config entry that exposes every tool of the five servers. It starts the time tracker, price tracker, spreadsheet, invoice and expense tracker as child processes and exposes every tool, resource and prompt under one server, with one license pair.

One entry in claude_desktop_config.json instead of five, which matters more here than anywhere else: this is the client where each extra server is another absolute path to get right.

What you get in Claude Desktop

You say	Tool
Start a timer for Acme.	`timer_start`
Now invoice Acme for this week's hours and the rebillable expenses, 23% VAT, due in 14 days, PDF.	`six calls, entry_list through invoice_pdf`
What did I spend this month and what is still unbilled?	`expense_list and entry_list`

Its startup line reads: proxying [time-tracker, price-tracker, spreadsheet, invoice, expense-tracker], 49 tools. Those three sentences are consecutive turns of one audited conversation that scored 12 out of 12.

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`

{
  "mcpServers": {
    "office-suite": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-office-suite"]
    }
  }
}

If node came from nvm, asdf or homebrew, replace "npx" with the absolute path that which npx prints:

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

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

The npm publish of @theluckystrike/mcp-office-suite is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

The suite starts five child processes, so it has no hosted form. Each of the five is served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP instead: mint a free token with curl https://mcp.zovo.one/mcp/token, 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 npx` 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 npx 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 Cline and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs