[Help wanted] Write a First MCP tool call blog post / dev.to tutorial — companion to alpha launch

[hoainho]

🌟 Before claiming this issue

Two quick steps before you open a PR:

1. ⭐ Star the repository — low-friction signal that you'll follow through
2. 💬 Comment I'll take this (or similar) below — prevents two contributors racing on the same issue

Full policy: CONTRIBUTING.md → How to claim. If a claim is older than 7 days with no PR, you can reclaim it politely.

---

Context

M4 alpha ship needs a launch narrative. A dev.to or personal-blog tutorial walking through setting up Claude Desktop, installing react-debugger MCP, and asking the agent a real question about a real React bug would dramatically lower the trial barrier for first-time users.

Where to look

• The full alpha flow lives in cli/docs/MCP_USAGE.md (built in task 5.2)
• The growth proposal at openspec/changes/growth-and-contributor-attraction/ names dev.to / Hashnode / Medium as primary launch channels

Expected outcome

• A published dev.to post (cross-post Hashnode and Medium with dev.to canonical)
• Article structure: hook, install, first tool call, real debugging session, call-to-action
• Article includes 2 to 3 screenshots and one short GIF of the agent debugging a real React app
• Article opens with maintainer attribution (this is OSS; community contributors with bylines welcome)
• Article links back to the GitHub repo

Estimated effort

M (3 to 6h)

How to claim

Comment "@hoainho I will take this" to claim. Share your dev.to handle. PR within 14 days or unclaimed (PR target is the README, which links the published article).

Acceptance criteria

• Article URL published and live
• README "MCP for Agents" section links to it
• Article uses the same install command plus mcp.json snippets as cli/docs/MCP_USAGE.md (no drift)
• If maintainer agrees, the article is cross-posted under both names with a co-authored tag