mirror of
https://github.com/anthropics/claude-plugins-official.git
synced 2026-04-28 21:25:31 +00:00
f227eeb90c
Local-path plugins (source is a string like "./plugins/foo" in
marketplace.json) without a manifest version cache at
~/.claude/plugins/cache/{marketplace}/{plugin}/unknown/ forever.
The cache check in claude-cli's copyPluginToVersionedCache sees
pathExists(.../unknown/) → true → skips re-extraction, even after
the marketplace content updates. Users are stuck with stale plugin
files until they manually delete the cache.
Adding "version": "1.0.0" fixes this because calculatePluginVersion
reads the manifest from the freshly-synced marketplace tree (not the
stale cache), and manifest.version is priority #1 in version
resolution. New version → new cache path → cache miss → re-extract.
This is preferable to the GCS-SHA fallback approach
(anthropics/claude-cli-internal#24773) because:
- Per-plugin granularity: only bumped plugins re-extract, not all
27 on every marketplace push
- No disk accumulation from unrelated marketplace churn
- Fixes both the runtime loader path AND the migration path
(manifest.version is priority #1 in both)
- No claude-cli code change needed
Remote-sourced plugins (github/git/url) already get a git SHA as
their version and are unaffected.
mcp-server-dev
Skills for designing and building MCP servers that work seamlessly with Claude.
What's inside
Three skills that compose into a full build path:
| Skill | Purpose |
|---|---|
build-mcp-server |
Entry point. Interrogates the use case, picks deployment model (remote HTTP / MCPB / local stdio), picks tool-design pattern, routes to a specialized skill. |
build-mcp-app |
Adds interactive UI widgets (forms, pickers, confirm dialogs) rendered inline in chat. Works on remote servers and MCPB bundles. |
build-mcpb |
Packages a local stdio server with its runtime so users can install it without Node/Python. For servers that must touch the local machine. |
How it works
build-mcp-server is the front door. It asks what you're connecting to, who'll use it, how big the action surface is, and whether you need in-chat UI. From those answers it recommends one of four paths:
- Remote streamable-HTTP (the default recommendation for anything wrapping a cloud API) — scaffolded inline
- MCP app — hands off to
build-mcp-app - MCPB — hands off to
build-mcpb - Local stdio prototype — scaffolded inline with an MCPB upgrade note
Each skill ships reference files for the parts that don't fit in the main instructions: auth flows (DCR/CIMD), tool-description writing, widget templates, manifest schemas, security hardening.
Usage
Ask Claude to "help me build an MCP server" and the entry skill will trigger. Or invoke directly:
/mcp-server-dev:build-mcp-server