Generate MCP Server Card

Generate an MCP server card JSON file in the mcp-gateway-registry format by analyzing the source code at $ARGUMENTS.

This format is used by https://github.com/agentic-community/mcp-gateway-registry for registering MCP servers in the gateway registry.

Steps

1. Carefully study the source code

Do NOT just skim the top-level files. MCP servers can be complex, multi-file projects. You MUST thoroughly explore the entire folder structure before generating the card.

If $ARGUMENTS is a local folder path, use Glob to find ALL Python files, YAML/JSON configs, and README files in the folder and its subfolders. Read every relevant file.

If $ARGUMENTS is a GitHub URL, use WebFetch to read the raw file contents. Follow imports to discover additional files.

Where to look (MCP servers are not always a single file):

• Entrypoints: main.py, app.py, server.py, __main__.py, mcp_server.py
• Tool definitions: look for @mcp.tool(), @server.tool(), @tool, tool handler functions, tool registrations
• OpenAPI specs: .json or .yaml files in openapi-specs/, specs/, api/ folders - these define the tools when an API is exposed as MCP
• Config files: pyproject.toml, requirements.txt, .bedrock_agentcore.yaml, deploy_*.py, docker-compose.yml
• Deployment scripts: these reveal the gateway URL, auth scheme, transport type
• Gateway configs: .deployment_info.json, .roo.json - these have the actual MCP endpoint URL
• Sub-folders: check ALL subdirectories for additional tools, resources, or shared utilities
• Resource definitions: MCP servers can expose resources and prompts in addition to tools

From the code, detect: