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.
Five servers' worth of tools arrive as one entry, so mcp.json holds one object with one required type field instead of five, and the Customize page lists one server to enable or disable.
| 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.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
{
"mcpServers": {
"office-suite": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-office-suite"]
}
}
}The Customize page shows the server and its tools once it has started.
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.
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.
The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: each child keeps its own free tier. Pro is $39 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Office Suite pasting the config block above is the supported route.
The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs