generate-server-card

Generate MCP server card JSON configs by analyzing server source code.

892|225|Updated May 29, 2025
One-click install
npx skills add https://github.com/agentic-community/mcp-gateway-registry --skill generate-server-card
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-server-card
Source: https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/generate-server-card
Command: npx skills add https://github.com/agentic-community/mcp-gateway-registry --skill generate-server-card

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about generate-server-card

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

FAQPage Schema
How do I generate an MCP server card for the mcp-gateway-registry?

Provide a local folder path or GitHub URL containing the MCP server source code. The Skill explores all files, detects the server name, tools, transports, and auth scheme, then writes a validated server card JSON in the registry format.

What fields are required in an MCP server card JSON?

Required fields are server_name, description, path (starting with /), proxy_pass_url, tags, and supported_transports. Optional fields include auth_scheme, mcp_endpoint, version, status, visibility, provider info, license, and num_tools.

Can it analyze an MCP server hosted on GitHub?

Yes, it accepts a GitHub URL as input and uses WebFetch to read raw file contents, following imports to discover additional files. Local folder paths are explored with Glob and file reads instead.

Why is tool_list empty in the generated server card?

The registry format intentionally omits individual tool entries, so tool_list is always set to an empty array. The Skill still counts detected tools and records the total in the num_tools field for informational purposes.

How does it detect the MCP server transport and auth scheme?

Transport is inferred from the server framework configuration, defaulting to streamable-http for gateway-deployed servers, with sse and stdio as alternatives. Auth is detected from deployment scripts and middleware, identifying bearer JWT, API key, OAuth2, Cognito, or none.