Office Suite All Servers One Install MCP server
One install that runs every sibling MCP server as a child process and merges their tools behind one
0 stars
Reviews
Write oneNobody has reviewed Office Suite All Servers One Install yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Office Suite All Servers One Install tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 19 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year5/10
How Office Suite All Servers One Install compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
Install Office Suite All Servers One Install in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Office Suite All Servers One Install repository's README, as published. We do not edit it. Read it on GitHub
mcp-office-suite
<!-- mirror-seo:start -->
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 45 hosted servers, 418 of them.
Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine: this one has no hosted endpoint, so install it from the bundle or from source.
Install
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 buildThen 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.
<!-- mirror-seo:end -->
In the official MCP Registry (io.github.theluckystrike/office-suite-time-invoice-expense-excel-price).
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://toolsmap 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 licensestatus / 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 (claudedesktopconfig.json):
{
"mcpServers": {
"office-suite": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-office-suite"]
}
}
}Claude Code:
claude mcp add office-suite -- npx -y @theluckystrike/mcp-office-suiteCursor (.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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Office Suite All Servers One Install: common questions
- Is Office Suite All Servers One Install MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Office Suite All Servers One Install safety report
- Does Office Suite All Servers One Install need an API key?
- Yes. The registry entry asks for
MCP_LICENSE_KEY. - Is Office Suite All Servers One Install maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.21.0.
- What can I use instead of Office Suite All Servers One Install?
- Servers from other publishers that do the same job: Qase Test Management MCP server.
Alternatives to Office Suite All Servers One Install
Same job from other publishers: the closest match first, then the best rated.
- Qase Test ManagementOfficial MCP server for Qase — manage test cases, runs, suites, defects via AI tools.not reviewedEstablishedA