Skip to content

v0.7.1 — discoverability + MCP Registry submission

Latest

Choose a tag to compare

@tathagat22 tathagat22 released this 24 May 23:13
· 36 commits to main since this release

Patch release that ships the discoverability work missing from v0.7.0's npm publish, and registers Plumb on the MCP Registry.

What's new

  • MCP Registry — Plumb is now searchable as `io.github.tathagat22/plumb-mcp` on registry.modelcontextprotocol.io. Clients that read the Registry (Cursor, Claude Code marketplaces, smithery, etc.) will surface Plumb automatically.
  • package.json — `mcpName` ownership marker added; description rewritten with failure-mode framing; keywords expanded 5 → 21 (`figma-mcp`, `mcp-server`, `claude-mcp`, `cursor-mcp`, `windsurf`, `figma-rate-limit`, `anthropic`, `design-tokens`, `verification`, …).
  • READMEs (en + zh + ja + ko) — new "Are you hitting one of these?" section listing the exact error strings (Dev Mode MCP 25k token cap, 6 calls/month limit, Framelink HTTP 429, Variables API requires Enterprise) so coding agents searching for those errors find Plumb.
  • Docs site — new `/alternatives` SEO landing page; hero refreshed to lead with the verification loop; troubleshooting cross-links to alternatives for inbound errors.
  • MCP server self-description — `instructions` and `plumb_status` description now name the failure modes Plumb bypasses, so any agent that calls `plumb_status` first immediately sees the positioning.
  • GitHub repo — description sharpened; topics expanded 12 → 18.

No code-behaviour changes

Everything from v0.7.0 (multi-agent connect, smarter inference) is unchanged. This is purely a discoverability and metadata release.

Install

```bash
npm install -g plumb-mcp@0.7.1
```