Kwork vs Claude Task Master

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

Kwork logoKworkDeveloper Tools · Local subprocess (stdio)Kwork freelance marketplace: browse projects, submit offers, manage orders, message clients52GoodAuth: not declaredClaude Task Master logoClaude Task MasterDeveloper Tools · Local subprocess (stdio)AI-powered task management system for AI-driven development. Features PRD parsing, task expansion, multi-provider support (Claude, OpenAI, Gemini, Perplexity, xAI), and selective tool loading for optimized context usage.61GoodAuth: api key required

Verdict: choose Kwork for developer tools work as a local process; choose Claude Task Master for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Kwork logoChoose Kwork when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: KWORK_WRITES, KWORK_EXPECTED_USER_ID, KWORK_SITE.
  • You want tools like account_status, get_connects, discover_projects.
Explore Kwork

Claude Task Master logoChoose Claude Task Master when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
Explore Claude Task Master

Feature & specification comparison

Rows where the two servers differ are marked.

SpecKwork logoKworkClaude Task Master logoClaude Task Master
CategoryDeveloper ToolsDeveloper Tools
Quality signal52/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsKWORK_WRITESKWORK_EXPECTED_USER_IDKWORK_SITEANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS
Verified ownerCommunity listingCommunity listing
GitHub stars328,270
Directory activity 0 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
Tools4Not listed

Tools & capabilities

Kwork tools 4

  • account_statusФактический account ID, binding, готовность writes и `unresolved_write_ids
  • get_connectsАктивные и общие коннекты
  • discover_projectsfavorites`, `all` или `category_ids`, фильтры и opaque cursor
  • list_notificationsПолные группы уведомлений

Claude Task Master 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.

Kwork

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kwork": {
      "command": "uvx",
      "args": [
        "kwork-mcp@1.5.2"
      ],
      "env": {
        "KWORK_WRITES": "YOUR_KWORK_WRITES_HERE",
        "KWORK_EXPECTED_USER_ID": "YOUR_KWORK_EXPECTED_USER_ID_HERE",
        "KWORK_SITE": "YOUR_KWORK_SITE_HERE"
      }
    }
  }
}

Claude Task Master

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "eyaltoledano-claude-task-master": {
      "command": "npx",
      "args": [
        "-y",
        "task-master-ai"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
        "PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
        "XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
        "OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
        "MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE",
        "TASK_MASTER_TOOLS": "YOUR_TASK_MASTER_TOOLS_HERE"
      }
    }
  }
}

Frequently asked questions

Kwork is categorized under Developer Tools and uses a local stdio subprocess. Claude Task Master belongs to Developer Tools and uses a local stdio subprocess. Pick Kwork for developer tools work and Claude Task Master for developer tools.

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.

Kwork has no declared pricing — check the project's own site. Claude Task Master is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 kwork and eyaltoledano-claude-task-master as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Kwork has a quality signal of 52/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Claude Task Master has 61/100 (Good) with 10 views, 0 installs and 28,270 GitHub stars.