MCP Registry Publisher

ProductivityIntermediate

Checks required registry fields, versioning policy, documentation links, and security metadata before publishing.

Trigger/mcp-publish

Frequencyper 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

MCPRegistryPublishingMetadata

How It Works

/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

Skill Code

# 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]
---

Copy and paste into your CLAUDE.md to start using immediately.

How MCP Registry Publisher Works

MCP Registry Publisher reads your server's manifest files (mcp-server.json, package.json) and validates required fields across four categories — metadata, versioning policy, documentation links, and security metadata — in parallel. It then generates a submission-ready registry payload and a detailed validation report.

When to Use MCP Registry Publisher

Most useful before publishing your MCP server to the official registry or when integrating into CI to gate deployments on registry compliance. Catches missing metadata before submission to prevent rejection.

Key Strengths

Automated validation against Registry v0.1 API spec
Four-category parallel checks for fast feedback
Auto-generates submission-ready manifest
CI pipeline integration for release quality gates

Same Category

Productivity View All

CLAUDE.md Builder

Analyzes your project and auto-generates an optimized CLAUDE.md.

Dependency Audit

Analyzes project dependencies for security vulnerabilities and updates.

Project Onboarding

Quickly maps out a new project's structure and core logic.

Popular in Other Categories

Session Summary

WorkflowAutomatically summarizes changes and next steps at the end of a work session.

Smart Commit

CodingAnalyzes changes and auto-generates meaningful commit messages.

API Design Assistant

DocumentationDesigns RESTful APIs and auto-generates docs and type definitions.