create-mcp-md

You can generate mcp.md documentation by parsing an existing mcp.json to extract server configurations, command/args, and headers, then writing the output with accurate frontmatter to match registry conventions.

Creating registry-ready MCP server documentation involves extracting server settings and optional inputs from mcp.json and translating them into a standardized mcp.md format with correct frontmatter and headers.

Documentation gathering works by pulling tool descriptions from existing README files, upstream documentation, or --help command output, and prompting for missing URL information when necessary.

Yes, you can use mcp.json settings to add new MCP server entries by converting server names, type/url, environment variables, and inputs directly into the registry's required mcp.md format.

You need to generate mcp.md files when adding new MCP server entries to the yoke-registry, ensuring the resulting documentation matches the expected convention and includes accurate configuration details.

Mcp.md generation only adds skills entries when a matching skill name already exists to prevent invented or incorrect references, ensuring registry-safe linking within the documentation.