add-mcp-server

To create a compliant server.json file for an MCP registry, you need to ensure proper schema adherence, version pinning, and correct _meta extensions for provenance metadata. The add-mcp-server Skill automates generating this structured file for both container and remote servers.

MCP server onboarding metadata requires a structured server.json that includes naming conventions, repository details, version pins, and aligned _meta extensions. It also needs an icon.svg file to complete the registry entry and pass validation.

To add a container-based MCP server to ToolHive, provide the server name, type, repository, and metadata details. The onboarding workflow will generate the required server.json and icon.svg files while enforcing naming rules and validating the final schema.

Yes, an icon.svg file is required to validate your MCP registry entry. The onboarding process creates the icon reference and validates the overall registry metadata alongside the server.json file to ensure full schema compliance.

Yes, the MCP registry schema supports remote servers. The generation workflow covers both container-based and remote server types, guiding naming, templating, and validation to ensure proper _meta extensions and provenance metadata alignment.

Your MCP server.json might fail schema validation due to misaligned _meta extensions, missing provenance metadata, incorrect naming rules, or unpinned version numbers. The onboarding workflow enforces these rules to ensure the final JSON conforms to the server schema.