smithery-manifest

To auto-generate an MCP Registry server manifest, the skill reads your canonical skills.json, aeon.yml, and mcp-server/package.json to produce deterministic discovery artifacts. It creates the JSON manifest directly from the tool catalog so your tools become discoverable in pickers.

The best way to create Smithery deployment config for a stdio MCP server is to auto-generate it from your existing project files. The skill reads your skills catalog and package.json to output deterministic, paste-ready submission documentation.

Auto-generating Smithery submission docs works by reading skills.json, aeon.yml, mcp-server/package.json, and README to derive per-skill enablement and scheduling semantics. It then writes deterministic documentation outputs and only notifies the maintainer when artifacts change.

You do not need to manually update MCP Registry listings when adding new tools. Running the skill regenerates the manifest and submission files from the current skills.json, ensuring your tool catalog and per-skill enablement semantics stay synchronized without hand authoring.

You can maintain an up-to-date tool catalog for MCP discovery pickers automatically by running the skill. It derives per-skill enablement and cron/on-demand scheduling semantics from skills.json and writes the updated manifest artifacts required for listing.

Your MCP Registry manifest falls out of sync when skills.json is updated manually without regenerating the discovery artifacts. Running the skill reads the current catalog and configuration files to write deterministic docs outputs, notifying you only when the generated artifacts change.