Google MCP Suite vs KitchenSink4Word
A side-by-side look at the Google MCP Suite and KitchenSink4Word MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google MCP Suite for workplace & productivity work as a local process; choose KitchenSink4Word for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google MCP Suite when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GOOGLE_MCP_ACCOUNT.
Choose KitchenSink4Word when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 57/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_MCP_ACCOUNT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 11 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google MCP Suite | View KitchenSink4Word |
Tools & capabilities
Google MCP Suite tools
No tool names declared yet. Check the project README from the listing page.
KitchenSink4Word 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.
Google MCP Suite
{
"mcpServers": {
"google-mcp-suite": {
"command": "npx",
"args": [
"-y",
"google-mcp-suite"
],
"env": {
"GOOGLE_MCP_ACCOUNT": "YOUR_GOOGLE_MCP_ACCOUNT_HERE"
}
}
}
}
KitchenSink4Word
{
"mcpServers": {
"kitchensink4word": {
"command": "uvx",
"args": [
"kitchensink4word"
]
}
}
}
Frequently asked questions
Google MCP Suite is categorized under Workplace & Productivity and uses a local stdio subprocess. KitchenSink4Word belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Google MCP Suite for workplace & productivity work and KitchenSink4Word for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google MCP Suite has no declared pricing — check the project's own site. Auth: oauth 2.0. KitchenSink4Word has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-mcp-suite and kitchensink4word as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google MCP Suite has a quality signal of 57/100 (Good) with 2 views, 0 installs and 5 GitHub stars. KitchenSink4Word has 43/100 (Fair) with 0 views, 0 installs and 11 GitHub stars.