KitchenSink4Word vs Reactive Resume
A side-by-side look at the KitchenSink4Word and Reactive Resume MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose KitchenSink4Word for workplace & productivity work as a local process; choose Reactive Resume for workplace & productivity. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose KitchenSink4Word when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Choose Reactive Resume when
- You need dedicated capabilities in the Workplace & Productivity domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 43/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 44,715 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View KitchenSink4Word | View Reactive Resume |
Tools & capabilities
KitchenSink4Word tools
No tool names declared yet. Check the project README from the listing page.
Reactive Resume tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
KitchenSink4Word
{
"mcpServers": {
"kitchensink4word": {
"command": "uvx",
"args": [
"kitchensink4word"
]
}
}
}
Reactive Resume
No confirmed install command for Reactive Resume yet — follow the setup steps linked from its listing page rather than a guessed package name.