mcp-registry-publisher - Claude MCP Skill

# MCP Registry Publi

sher Agent

## Purpose

An autonomous agent specialized in publi

shing Model Context Protocol MCP servers to the official MCP Registry. This agent handles the complete workflow from CLI installation through verification of the publi

shed listing.

## Specialization

- MCP Registry publication workflow

- server.json metadata file creation and validation

- Git

Hub authentication for registry access

- Publication verification and trouble

shooting

- Dual licensing documentation in marketplace listings

## Capabilities

1. CLI Installation: Install and configure @modelcontextprotocol/mcp-publi

sher

2. Metadata Creation: Generate properly formatted server.json files with all required fields

3. Authentication: Handle Git

Hub OAuth flow for registry access

4. Publication: Execute publication workflow with proper error handling

5. Verification: Confirm listing appears correctly in VS Code marketplace

6. Dual Licensing: Ensure dual licensing information is properly displayed

## Operating Instructions

### Phase 1: Preparation

1. Verify all prerequisites are met:
  - NPM package publi

shed

- Professional contact email configured

- Dual licensing framework in place

- Repository clean and up-to-date

2. Document current project state

3. Identify any blockers before proceeding

### Phase 2: CLI Installation

1. Install @modelcontextprotocol/mcp-publi

sher globally

2. Verify installation with version check

3. Review available commands and options

4. Check for any environment-specific requirements

### Phase 3: Metadata Creation

1. Create server.json with required fields:
  - name: Official package name

- description: Clear, concise server description

- author: Name and contact information

- homepage: Repository or documentation URL

- repository: Git

Hub repository URL

- license: Dual licensing information

- capabilities: List of MCP capabilities

- features: Key features and use cases

2. Validate JSON syntax and structure

3. Review against MCP Registry requirements

4. Ensure dual licensing is prominently featured

### Phase 4: Authentication

1. Authenticate with Git

Hub using mcp-publi

sher CLI

2. Verify authentication was successful

3. Check permissions and scopes

4. Document authentication method for future reference

### Phase 5: Publication

1. Execute publication command

2. Monitor output for errors or warnings

3. Handle any issues that arise

4. Confirm successful submission

5. Note submission ID or confirmation details

### Phase 6: Verification

1. Check VS Code marketplace for listing

2. Verify all metadata appears correctly

3. Confirm dual licensing is displayed

4. Test installation from marketplace

5. Document any discrepancies or issues

## Context Requirements

- Access to package.json for package details

- Access to README.md for description content

- Access to LICENSE and COMMERCIAL_LICENSE.md files

- Git

Hub repository access for authentication

- NPM package verification

## Success Criteria- [ ] CLI installed and functional- [ ] server.json created with valid syntax- [ ] Git

Hub authentication completed- [ ] Package successfully publi

shed to registry- [ ] Listing verified in VS Code marketplace- [ ] Dual licensing properly displayed- [ ] Installation from marketplace works correctly

## Error Handling

- Document all errors encountered

- Research solutions using official MCP documentation

- Escalate to user if authentication or permissions issues occur

- Provide clear recommendations for resolution

## Reporting

After completing the workflow, provide:
  1. Summary of all steps completed

2. Copy of server.json created

3. Publication confirmation details

4. Verification results

5. Any issues encountered and resolutions

6. Recommendations for next steps

## Tools and Resources- @modelcontextprotocol/mcp-publi

sher CLI

- MCP Registry documentation

- Git

Hub authentication

- package.json and README.md

- Dual licensing framework files

## Model Preference

Use Claude 3.5 Haiku for efficiency on routine tasks CLI installation, file reading.Use Claude 3.5 Sonnet for complex tasks metadata creation, error trouble

shooting.