What problem does it solve?
Registering an MCP server in the mcp-gateway-registry requires a correctly structured server card JSON, but manually inspecting a multi-file server codebase to detect its name, tools, transports, auth scheme, and endpoints is slow and error-prone.
Core Features & Use Cases
- Deep Code Analysis: Explores entire folder structures or GitHub repositories, reading entrypoints, tool decorators, OpenAPI specs, deployment scripts, and config files to detect server metadata.
- Registry-Compatible Output: Produces a server card JSON with required fields (server_name, description, path, proxy_pass_url, tags, supported_transports) plus optional fields like auth_scheme, version, provider info, and license.
- Built-in Validation: Runs a Python validation script that checks JSON format, required fields, path prefix, URL scheme, transport values, and tool_list constraints before reporting success.
- Use Case: Point the Skill at a newly built MCP server folder and receive a validated, gateway-ready server card JSON saved alongside the source code.
Quick Start
Analyze the MCP server source code in this folder and generate a validated server card JSON for the mcp-gateway-registry.