MCP Server Analysis
Analyze an MCP server's source code to extract tools, classify its architecture pattern, and assess CLI conversion feasibility.
How to Analyze
Read the MCP server source code and extract:
- Tools: List every
@tool,server.setRequestHandler(CallToolRequestSchema, ...), or@mcp.tool()definition - Parameters: For each tool, document all input parameters (name, type, required/optional, description)
- Output format: What each tool returns (JSON structure, text, binary)
- Dependencies: External APIs, SDKs, auth requirements
- Transport: stdio, SSE, HTTP — and whether the server is a proxy or direct implementation
- Resources/Prompts: Any MCP resources or prompt templates exposed
Output Format
Create a structured analysis table:
| Tool Name | Params | Output | API Endpoint | Auth |
|-----------|--------|--------|--------------|------|
Then classify the server using references/pattern-classification.md and report:
- Pattern type and tier (1-4)
- CLI conversion feasibility (Excellent / Good / Partial / Not recommended)
- Recommended conversion strategy
- Any blockers or concerns