KitchenSink4Word vs Clickup

A side-by-side look at the KitchenSink4Word and Clickup MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

KitchenSink4Word logoKitchenSink4WordWorkplace & Productivity · Local subprocess (stdio)Everything and the kitchen sink for Word: tables, citations, footnotes, TOC, tracked changes.43FairAuth: not declaredClickup logoClickupWorkplace & Productivity · Local subprocess (stdio)Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.49FairAuth: not declared

Verdict: choose KitchenSink4Word for workplace & productivity work as a local process; choose Clickup 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?

KitchenSink4Word logoChoose KitchenSink4Word when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
Explore KitchenSink4Word

Clickup logoChoose Clickup when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
Explore Clickup

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKitchenSink4Word logoKitchenSink4WordClickup logoClickup
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal43/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1152
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

KitchenSink4Word tools

No tool names declared yet. Check the project README from the listing page.

Clickup 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kitchensink4word": {
      "command": "uvx",
      "args": [
        "kitchensink4word"
      ]
    }
  }
}

Clickup

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "clickup-2": {
      "command": "npx",
      "args": [
        "-y",
        "@taazkareem/clickup-mcp-server@latest"
      ]
    }
  }
}

Frequently asked questions

KitchenSink4Word is categorized under Workplace & Productivity and uses a local stdio subprocess. Clickup belongs to Workplace & Productivity and uses a local stdio subprocess. Pick KitchenSink4Word for workplace & productivity work and Clickup 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.

KitchenSink4Word has no declared pricing — check the project's own site. Clickup 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 kitchensink4word and clickup-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, KitchenSink4Word has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 11 GitHub stars. Clickup has 49/100 (Fair) with 2 views, 0 installs and 52 GitHub stars.