docs(readme): add MCP decision table + stop presenting hosted endpoint as this server

[johnxie]

Summary

The root README mixes two MCP surfaces. Its "Zero-install (hosted)" blockquote (line ~54) presents https://www.taskade.com/mcp as a tokenless path to this Workspace MCP server — but per the Taskade docs, that endpoint is the Genesis App MCP, a separate hosted surface (OAuth, Business+) that edits app source and is read-only on content. This PR adds a "Which Taskade MCP do I want?" decision table and recharacterizes the hosted block as the separate surface it is.

What changed

Location	Before	After
L~54 blockquote	"Zero-install (hosted)… nothing to install, no token… full workspace access" implying this server	"Prefer a hosted option? …/mcp is the Genesis App MCP, a separate hosted surface; for workspace content use this Workspace MCP server"
(new section)	—	"Which Taskade MCP do I want?" 3-row decision table

⚠️ Reviewer decision needed (@deanzaka @lxcid)

This change assumes https://www.taskade.com/mcp is the Genesis App MCP (OAuth, Business+, edits app source, read-only on content) — which is what the taskade/docs guides state. The current README instead describes that endpoint as a zero-install path to full workspace access. These two descriptions contradict each other. Please confirm the hosted endpoint's true behavior before merge:

• If the docs are right → this PR is correct.
• If the README is right (there really is a hosted, tokenless Workspace MCP at that URL) → we should fix the docs instead, and I'll revise this PR.

Wording here is deliberately conservative (defers behavioral detail to the linked guide) so it's correct under the most likely reading and easy to adjust.

Design lens

Geist (mirror the docs' canonical 3-surface model) + Atkinson (don't offer the wrong door first).

Merge order

Touches the root README near L54; M2 edits L3/L48/L272/links (separate hunks). Merge M1 → M2.

---

Verified baseline: @taskade/mcp-server@0.1.1 · 62 tools (57 v1 + 5 v2) · canonical endpoint https://www.taskade.com/mcp.

🤖 Authored with Claude Code (multi-agent verified)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 73cbec0

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]

Review

Approve — with one explicit decision point for the maintainers (below).

Verification notes:

• Scope is clean. Only README.md is touched; the hunk is a +10-line block around the hosted-endpoint blockquote. L48 and L272 are untouched and owned by docs(readme): align name to "Workspace MCP", deep-link guides, qualify full-access claims #63 (M2) — no overlap.
• Links resolve. Both deep-link targets exist in taskade/docs: apis-living-system-development/genesis-app-mcp.md and genesis-living-system-builder/genesis/mcp-connectors.md. Endpoint https://www.taskade.com/mcp and the token-page reference are canonical.
• Hosted-endpoint wording is safely conservative. The blockquote characterizes the endpoint as the OAuth-protected Genesis App MCP and a "separate hosted surface," then defers all behavioral detail to the linked guide rather than over-claiming. The decision-table rows are accurate to the 3-surface model.

⚠️ Reviewer decision needed (@deanzaka @lxcid): this PR assumes https://www.taskade.com/mcp is the Genesis App MCP (OAuth, Business+, edits app source, read-only on content), per the taskade/docs guides. The README previously described that same endpoint as a zero-install path to full workspace access — the two descriptions contradict each other. Please confirm the hosted endpoint's true behavior before merge:

• If the docs are right → this PR is correct as-is.
• If a hosted, tokenless Workspace MCP really exists at that URL → we should fix the docs instead, and I'll revise this PR. The wording here was kept deliberately conservative so it's correct under the most likely reading and easy to adjust.

Reviewed via a two-lens pass (pr-review-toolkit:code-reviewer + an independent doc-correctness/link verifier) with adversarial verification.

cc @deanzaka @lxcid