docs(readme): align name to "Workspace MCP", deep-link guides, qualify full-access claims

[johnxie]

Summary

Three small consistency fixes to the root README: (1) the docs call this server the Workspace MCP but the README calls it "Taskade MCP Server" — reads as two products; (2) the README links only the docs home, giving a reader no path to the specific guides; (3) "full access to your workspace" / "Full workspace management" over-promise on free plans (some endpoints are gated).

What changed

Location	Before	After
H1 (L~3)	# Taskade MCP Server	+ subtitle: "The Workspace MCP (@taskade/mcp-server)…"
Use-case cell (L~48)	"Full workspace management from your AI assistant"	+ "(paid plans; some endpoints gated on free)"
Prose (L~272)	"full access to your workspace"	"access to your workspace" + plan-gating parenthetical
Resources (L~495/535)	only docs.taskade.com	+ deep-links to the Workspace MCP guide & Genesis App MCP guide

Why it matters (the David cohort)

"Taskade MCP Server" vs "Workspace MCP" reads as two products; the reader has no path from the repo to the operator guides; and "full access" sets a false expectation that breaks on a free plan.

Design lens

Geist — consistency = recognizability. One product, one name, honest expectations.

Verification / zero-regression

• npm package name unchanged; H1 preserved (subtitle added).
• Both "full access" locations edited (editing only one would leave the README self-contradictory).
• Deep-links use guaranteed-valid github.com/taskade/docs source URLs; a maintainer may swap to canonical docs.taskade.com slugs.
• Line ~54 hosted block + decision table are owned by M1; packages/server/README.md by M3 — not touched here.

Merge order

Merge M1 → M2 (both touch the root README, separate hunks).

---

🤖 Authored with Claude Code (multi-agent verified)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 233811c

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

No blocking issues found — verified links resolve, claims match the shipped 62-tool / 3-surface ground truth, and the change stays in scope.

Verification notes:

• Scope: only README.md changed (+6/-2). packages/server/README.md (docs(server): replace stale package README with a stub linking the canonical sources #64, M3) and the hosted block + decision table (docs(readme): add MCP decision table + stop presenting hosted endpoint as this server #62, M1) are untouched; canonical endpoint/token strings unchanged.
• H1 # Taskade MCP Server preserved; subtitle added as a blockquote, npm package name unchanged.
• Both "full access" locations qualified — the use-case cell and the prose paragraph; no unqualified instance remains.
• Both deep-link targets return HTTP 200 (taskade/docs/.../workspace-mcp.md and .../genesis-app-mcp.md); Genesis App MCP correctly labeled "a different, hosted surface."

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

cc @deanzaka @lxcid