Conversation
Reorders the 'Which MCP' table: hosted /mcp first, stdio npm as offline fallback. Fixes tier claim (Starter+, not Business+). Adds 'Add to Cursor' config block at the top. Clarifies 62 vs 32 tool count. Updates privacy section to list v2 as primary. The 164-star mcp repo is the developer brand. The old README sent Cursor users to the v1 stdio wrapper (no write_file, no inspect_space) and called the hosted server a separate product. This fixes the single biggest developer-surface confusion. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Impact@deanzaka - this rewrites the README of our 164-star MCP repo to be hosted-MCP-first. The current README sends Cursor users to the v1 stdio wrapper (no Before/AfterQA
|
Aligns with Copilot review on taskcade#29493: the stdio npm package makes network requests and is not offline-capable. Co-authored-by: Cursor <cursoragent@cursor.com>
Code reviewFound 1 issue:
Lines 219 to 221 in c469660 🤖 Generated with Claude Code - If this code review was useful, please react with 👍. Otherwise, react with 👎. |
44 Phase A Public API v2 ops plus 4 MCP-native tools. Aligns with taskcade#29494 so Cursor users are not told the hosted surface is 32. Co-authored-by: Cursor <cursoragent@cursor.com>
What
Rewrites the README so the hosted MCP at
taskade.com/mcpis the first thing a reader sees, and the stdio npm package is clearly labeled as the local/offline fallback.Why
This repo has 164 stars and is the developer brand for Taskade MCP. But the current README sends Cursor users to the v1 stdio wrapper (no
write_file, noinspect_space) and calls the hosted server a separate 'Genesis App MCP, Business+' product. That single confusion is the biggest developer-surface tax.Changes
Before/After
QA
@deanzakafor visibility on the developer-surface cleanup. This is the highest-impact copy change: 164 stars of confusion -> 164 stars of clarity.