Home · Setup · Claude Code

MCP Office Suite in Claude Code

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 `claude mcp add` instead of five, and one bundle key. The audited conversation that started a timer and finished with a rendered invoice ran entirely through this single server.

What you get in Claude Code

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 Code

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`

claude mcp add office-suite -- npx -y @theluckystrike/mcp-office-suite
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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 Code notes worth knowing first

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.

Questions

Which scope should I use for MCP Office Suite?

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.

Why did my first prompt ignore the server?

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.

Can I use MCP Office Suite without installing anything?

Not this one; it starts five child processes, so it runs locally over stdio. Three of the servers behind it are hosted at https://mcp.zovo.one/mcp if you want a no-install route.

The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs