Two changes to make Sipcode submission-ready for claude-plugins-community:
1. .mcp.json now uses npx for zero-setup install
Before: { "command": "sipcode-mcp" }
Problem: assumes sipcode-mcp is already on PATH. A marketplace user
who runs `/plugin install sipcode@claude-community` has NOT yet
installed the npm package. The plugin would appear installed but
the MCP server would fail to spawn with "command not found" —
reviewer-rejection-class bug.
After: { "command": "npx", "args": ["-y", "-p", "sipcode", "sipcode-mcp"] }
Plugin install → MCP works immediately. npx fetches the npm package
on first run, caches it. ~5-15s startup cost on first launch, then
fast. Users who want instant startup can still `npm install -g
sipcode` and the global binary takes precedence.
This does NOT affect Claude Desktop integration. Desktop uses
claude_desktop_config.json (separate file, separate config, manually
edited per README). Desktop users keep the documented direct-binary
config: { "command": "cmd", "args": ["/c", "sipcode-mcp"] }.
2. plugin.json polish
- Added "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json"
for editor autocomplete + validation pipeline.
- Added "displayName": "Sipcode" so the plugin picker UI shows
"Sipcode" instead of "sipcode" (the kebab-case name is still used
for namespacing; displayName is purely cosmetic).
- Bumped version 1.3.0 -> 1.3.1.
- Tightened description to lead with the auto-install story so
marketplace reviewers see "zero-setup" up front.
833/833 tests still pass. No code changes outside plugin manifest +
.mcp.json + package.json. Submission target after this lands:
- https://claude.ai/settings/plugins/submit
- https://platform.claude.com/plugins/submit
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>