smithery-manifest

Generate Smithery and MCP Registry manifests from skills catalog and server metadata.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill smithery-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smithery-manifest
Source: https://github.com/anajuliabit/aeon/tree/main/skills/smithery-manifest
Command: npx skills add https://github.com/anajuliabit/aeon --skill smithery-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes the manual, error-prone work of writing Smithery and MCP Registry submission text and manifests by generating them directly from the repo’s current skill catalog and MCP server metadata.

Core Features & Use Cases

  • Generates MCP Registry-compatible manifest JSON so Aeon’s MCP server can be listed with the correct tools catalog and metadata.
  • Generates Smithery deployment YAML to configure stdio-based startup for the MCP server with the right command wiring.
  • Produces a paste-ready submission document that keeps listing submissions consistent with the current skills.json catalog and aeon.yml enabled flags.

Quick Start

Run smithery-manifest to regenerate docs/smithery-manifest.json, docs/smithery.yaml, and docs/smithery-submission.md from skills.json, aeon.yml, mcp-server/package.json, and the README.

Frequently Asked Questions about smithery-manifest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate MCP Registry submission manifests from a skills catalog?

To auto-generate MCP Registry manifests from a skills catalog, run the tool to parse skills.json and package metadata, producing schema-compatible server.json files with correct tools catalog wiring.

How do I generate a Smithery deployment YAML for an MCP server?

Generating Smithery deployment YAML involves reading server package metadata to configure stdio-based startup commands, producing a deployment file with the correct command wiring for the MCP server.

Can I automate Smithery and MCP Registry documentation updates across version changes?

You can automate Smithery and MCP Registry documentation updates across version changes by running an idempotent diff check that opens at most one refresh PR per run to keep listings synchronized.

What do I need to prepare before generating MCP Registry and Smithery submission docs?

Before generating submission docs, you need a valid skills.json catalog, an aeon.yml configuration with enabled flags, mcp-server package.json metadata, and a README file in the repository.

Does generating Smithery manifests require manual editing of the server configuration?

Generating Smithery manifests does not require manual editing, as the process directly extracts tools catalog data and server metadata to produce a paste-ready submission document and configuration files.

Why are my MCP Registry listings out of sync with my current skills catalog?

MCP Registry listings fall out of sync with a skills catalog when manifest JSON is manually written and not regenerated after catalog updates or version changes, requiring automated generation to fix discrepancies.