Skip to content

docs: Rewrite README as hosted-MCP-first - #87

Open
johnxie wants to merge 3 commits into
mainfrom
docs/readme-hosted-first
Open

johnxie wants to merge 3 commits into
mainfrom
docs/readme-hosted-first

Conversation

@johnxie

@johnxie johnxie commented Sep 17, 2026

Copy link
Copy Markdown
Member

What

Rewrites the README so the hosted MCP at taskade.com/mcp is 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, no inspect_space) and calls the hosted server a separate 'Genesis App MCP, Business+' product. That single confusion is the biggest developer-surface tax.

Changes

  • Added hosted MCP 'Add to Cursor' config block at the top
  • Reordered 'Which MCP' table: hosted first, stdio second
  • Fixed tier claim: Starter+ (not Business+)
  • Added note clarifying 62 vs 32 tool count (hosted vs stdio)
  • Updated privacy section: v2 is primary, v1 is legacy
  • OpenAPI codegen section unchanged

Before/After

BEFORE:                              AFTER:
┌─────────────────────────┐         ┌──────────────────────────────┐
│ 62 tools (stdio first)  │         │ Quick Start (Hosted MCP)     │
│ Which MCP? (3 options)   │         │ Add to Cursor config block   │
│ stdio = primary         │         │ Which MCP? (hosted first)    │
│ hosted = Business+      │         │ stdio = offline fallback     │
└─────────────────────────┘         │ hosted = Starter+            │
                                      │ 62 tools (note: 32 hosted)   │
                                      └──────────────────────────────┘

QA

Step Action Expected
1 Open the PR diff README changes are clear
2 Read the first section Hosted MCP URL is first
3 Check the 'Which MCP' table Hosted is row 1, stdio is row 2
4 Check tier claim Says Starter+, not Business+
5 Check tool count note 32 hosted, 14 stdio
6 Check OpenAPI codegen section Unchanged

@deanzaka for visibility on the developer-surface cleanup. This is the highest-impact copy change: 164 stars of confusion -> 164 stars of clarity.

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>
@changeset-bot

changeset-bot Bot commented Sep 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5f65e32

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@johnxie

johnxie commented Sep 17, 2026

Copy link
Copy Markdown
Member Author

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 write_file, no inspect_space) and calls the hosted server a separate "Genesis App MCP, Business+" product. This fixes the single biggest developer-surface confusion.

Before/After

BEFORE:                              AFTER:
┌─────────────────────────┐         ┌──────────────────────────────┐
│ 62 tools (stdio first)  │         │ Quick Start (Hosted MCP)     │
│ Which MCP? (3 options)  │         │ Add to Cursor config block   │
│ stdio = primary         │         │ Which MCP? (hosted first)    │
│ hosted = "Business+"    │         │ stdio = "offline fallback"   │
│                         │         │ hosted = "Starter+"          │
│                         │         │ 62 tools (note: 32 hosted)   │
└─────────────────────────┘         └──────────────────────────────┘

QA

Step Action Expected
1 Read the PR diff Hosted MCP URL is first section
2 Check "Which MCP" table Hosted is row 1, stdio is row 2
3 Check tier claim Says "Starter+", not "Business+"
4 Check tool count note 32 hosted, 14 stdio
5 Check OpenAPI codegen section Unchanged
6 Check privacy section v2 listed as primary

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>
@johnxie

johnxie commented Sep 17, 2026

Copy link
Copy Markdown
Member Author

Code review

Found 1 issue:

  1. Hosted MCP tool count is stale at 32 (28 Public API v2 + 4 native). After taskade#29494 the hosted server registers 44 Phase A parity ops plus 4 MCP-native tools (48 total). Leaving 32 in the README will mislead Cursor users about what the hosted surface exposes.

mcp/README.md

Lines 219 to 221 in c469660

> **Tool count tracks the hosted server.** The hosted MCP at `/mcp` currently exposes 32 tools (28 Public API v2 ops + 4 MCP-native: `inspect_space`, `write_file`, `read_project`, `list_automations`). The stdio npm package in this repo wraps the v1 API and exposes 14 ops. For the full workspace surface including app-file editing, use the hosted URL above.

🤖 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants