Weeek MCP vs Kaneo

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

Weeek MCP logoWeeek MCPWorkplace & Productivity · Local subprocess (stdio)Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.45FairAuth: api key requiredKaneo logoKaneoWorkplace & ProductivityOfficial MCP server for Kaneo: manage tasks, projects, and labels from Claude and other MCP clients43FairAuth: not declared

Verdict: choose Weeek MCP for workplace & productivity work as a local process; choose Kaneo for workplace & productivity. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Weeek MCP logoChoose Weeek MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: WEEEK_ACCESS_TOKEN.
Explore Weeek MCP

Kaneo logoChoose Kaneo when

  • You need dedicated capabilities in the Workplace & Productivity domain.
Explore Kaneo

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWeeek MCP logoWeeek MCPKaneo logoKaneo
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal45/100 · Fair43/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthAPI key requiredNot declared
PricingNot declaredFree
Required env varsWEEEK_ACCESS_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars09,572
Directory activity 5 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Weeek MCP tools

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

Kaneo 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.

Weeek MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "weeek-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "weeek-mcp"
      ],
      "env": {
        "WEEEK_ACCESS_TOKEN": "YOUR_WEEEK_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Kaneo

No confirmed install command for Kaneo yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Weeek MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Kaneo belongs to Workplace & Productivity and uses an install path we have not confirmed yet. Pick Weeek MCP for workplace & productivity work and Kaneo 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. Kaneo has no confirmed install command yet — follow its own setup instructions.

Weeek MCP has no declared pricing — check the project's own site. Auth: api key required. Kaneo is listed as free. 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 weeek-mcp and kaneo as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Weeek MCP has a quality signal of 45/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Kaneo has 43/100 (Fair) with 3 views, 0 installs and 9,572 GitHub stars.