MCP Registry パブリッシャー

生産性中級

必須項目、バージョン方針、ドキュメントURL、セキュリティ情報をチェックして公開準備を整えます。

トリガー/mcp-publish

使用頻度per release

MCP Server Authorなら？ Run /mcp-publish before every release to catch missing metadata

DevOps Engineerなら？ Integrate into CI to gate deployments on registry compliance

MCPRegistry公開メタデータ

動作フロー

/mcp-publish [server-dir] run

↓

Phase 1: 4 validations in parallel

manifest-check

Validate required registry fields

version-policy

Check semver & compatibility

docs-links

Verify documentation URLs

security-meta

Audit auth & permission metadata

↓

Generate registry submission payload

↓

✓ Registry-ready manifest + validation report

スキルコード

# MCP Registry Publisher Skill
## Trigger: /mcp-publish [server-directory]

When invoked:

1. Read and validate mcp-server.json / package.json:
 - name, version (semver), description
 - transport type (stdio | streamable-http)
 - tools[] with inputSchema for each tool
 - author, license, repository URL

2. Check Registry-specific requirements:
 - README.md exists and has >200 chars
 - CHANGELOG.md or release notes link
 - Security: auth method declared (none | oauth | api-key)
 - Icon/logo URL (optional but recommended)
 - Minimum one example in examples/

3. Generate submission manifest:
---
## MCP Registry Submission Report

**Server**: [name]@[version]
**Transport**: [stdio | streamable-http]
**Tools**: [count] tools declared

### Validation Results
| Field | Status | Note |
|-------|--------|------|
| name | OK | Unique in registry |
| version | OK | 1.2.0 (semver) |
| tools | WARN | 2/5 missing descriptions |
| auth | OK | OAuth 2.1 declared |
| docs | FAIL | README < 200 chars |

### Ready to Submit?
[YES/NO] — [list of blocking issues]
---

コピーしてCLAUDE.mdに貼り付ければ、すぐに使えます。