Office Suite MCP Server

mcp-office-suite

MCP server for small business accounting and paperwork: invoices, PDFs, spreadsheets, Word documents, time tracking and expenses. One install that exposes every tool of all 31 servers, 292 of them.

Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.

Install

Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/office-suite over streamable-http and send the token as Authorization: Bearer <token>.

If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/office-suite/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.

Claude Desktop, one click. Download office-suite.mcpb from the latest release and double-click it.

From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.

git clone https://github.com/theluckystrike/mcp-office-suite.git
cd mcp-office-suite
npm install && npm run build

Then point your client at the built entry point:

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

@theluckystrike/mcp-office-suite is not published on npm yet, so an npx -y @theluckystrike/mcp-office-suite command will fail. The three paths above are the working ones and each is exercised by CI.

Read-only mirror of mcp-servers/servers/office-suite. See MIRROR.md.

One install for the whole freelancer office. This MCP server proxies all 31 sibling servers in this repository, so a client gets every one of their 292 tools behind a single config entry instead of 31. The child list is published at runtime as the office://tools_map resource, which is the only figure to trust: it is read from the running server, not from this file. Under the hood it starts each sibling as its own stdio child process, forwards tools/call, resources/* and prompts/* to whichever child owns the name, and merges their license state into one license_status / license_activate pair. Nothing is re-implemented: each child server runs exactly as it does standalone, with its own local JSON storage.

Every tool of time-tracker, price-tracker, spreadsheet and invoice, one claude mcp add.

60-second install

npm publish for @theluckystrike/mcp-office-suite (and its dependencies) is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path -- both are verified below. This server is packaged as office-suite.mcpb on release v0.2.1 and is listed on the official MCP registry (io.github.theluckystrike/office-suite-time-invoice-expense-excel-price).

One-click (.mcpb): download office-suite.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

Claude Desktop (claude_desktop_config.json):

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

Claude Code:

claude mcp add office-suite -- npx -y @theluckystrike/mcp-office-suite

Cursor (.cursor/mcp.json):

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

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these commands:

git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install
npm run build

npm run build (no -w) is required here -- it builds mcp-license and every sibling server that office-suite spawns as a child, then office-suite itself. Then point your client's command at node with one arg: the absolute path to servers/office-suite/dist/index.js.

To run every server in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key -- it is forwarded to every connected child. Activation is all-or-nothing: the reply is an error unless every child accepted the key, and it prints a per-child table (OK / FAILED with each child's own message) so a bundle that is half Pro cannot look like a success.

Why one server instead of thirty-one

Aggregation is what usage rewards in this category: the most-used server we track is a tool-aggregator gateway with 2,530 tools and 419,019 uses, 7.5x the next server and 30x the cohort median. A user who wants "office stuff" should not have to add thirty-one separate MCP servers to one client config. Installing this one gets every tool below.

Tools

Tool names are passed through unchanged from each child. If this bundle ever proxies two children that register the same tool name, both are exposed with a <child>_<tool> prefix instead -- the current renamed pairs are listed under Renamed tools below.

time-tracker

price-tracker

spreadsheet

invoice

Bundle-wide

Resources and prompts registered by any child (for example time-tracker's timetracker://today resource and daily_standup prompt) are also proxied under their original names.

Renamed tools

Two children can register the same tool name -- invoice and docx both have business_set. The bundle then exposes both, prefixed with the server they came from (invoice_business_set, docx_business_set), names the renames once on startup, and rewrites the child's own answer so a response that said "Run business_set ..." says the name you can actually call. The full mapping is published as the office://tools_map resource: exposed name -> child.tool, with the renamed pairs listed separately.

Free vs Pro

Each child server keeps its own free tier exactly as documented in its own README (see each servers/<name>/README.md). This bundle changes nothing about those limits -- it only changes how many config entries it takes to reach all of them.

A single bundle Pro key ($39 one-time, lifetime) unlocks Pro on every server in the bundle, instead of buying each server's $19 key separately. Activate it once here and it is forwarded to every child.

Get Pro: https://mcp.zovo.one/buy/bundle

Child processes

Each child runs as its own stdio process. Two things the proxy does on their behalf:

• Their stderr is drained into ours, one line at a time, tagged with the child it came from ([invoice] ...). A child's stderr is a pipe with a small OS buffer; left unread, a child that logged more than that buffer blocked in write() and the tool call it was answering never returned.
• A child that dies rejects its in-flight requests before the suite tries to restart it, so a proxied call fails fast instead of hanging until the client's timeout, where a retry could repeat a mutation that had already been applied.

Privacy

Every child server stores its data locally, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/<name>/ per server. This bundle adds no storage of its own and sends nothing anywhere; it only pipes stdio between your MCP client and the child processes it starts on your own machine.

expense-tracker

TODO: servers/expense-tracker/dist does not exist yet in this repository. Once that server is built and shipped, add it to CHILDREN in src/index.ts, its dependency to package.json, its build step to the Dockerfile, and its tool table to this README.

---

Built by theluckystrike (https://github.com/theluckystrike).