api-schema-analyzer
Analyze OpenAPI and Postman schemas for MCP tool generation. Use when analyzing API specifications, extracting endpoint information, generating tool signatures, or when user mentions OpenAPI, Swagger, API schema, endpoint analysis.
When & Why to Use This Skill
The API Schema Analyzer is a specialized Claude skill designed to automate the conversion of OpenAPI (Swagger) and Postman specifications into Model Context Protocol (MCP) tool definitions. By intelligently parsing complex API schemas, it extracts endpoints, parameters, and authentication requirements to generate type-safe function signatures, significantly accelerating the development of AI-powered integrations and agentic tools.
Use Cases
- Automated MCP Tool Generation: Rapidly transform OpenAPI/Swagger JSON or YAML files into functional tool signatures for AI agents, reducing manual configuration time.
- Postman Collection Migration: Parse existing Postman collections to extract request structures and map them directly to MCP-compatible tool definitions for immediate use.
- Type-Safe Code Generation: Generate Python or TypeScript function signatures with accurate type hints directly from API specifications to ensure robust and error-free API client development.
- API Endpoint Auditing: Extract and analyze comprehensive lists of endpoints, methods, and required parameters from complex schemas to facilitate documentation and integration planning.
| name | api-schema-analyzer |
|---|---|
| description | Analyze OpenAPI and Postman schemas for MCP tool generation. Use when analyzing API specifications, extracting endpoint information, generating tool signatures, or when user mentions OpenAPI, Swagger, API schema, endpoint analysis. |
| allowed-tools | Bash, Read, Write |
API Schema Analyzer
This skill analyzes OpenAPI/Swagger and Postman collection schemas to extract endpoint information for generating MCP tools.
Instructions
Analyzing OpenAPI Schemas
Load OpenAPI Spec
- Use script:
scripts/analyze-openapi.py <openapi.json|yaml> - Extracts: endpoints, methods, parameters, request/response schemas
- Use script:
Generate Tool Signatures
- Use script:
scripts/generate-tool-signatures.py <openapi.json> --lang=python|typescript - Creates: Function signatures with type hints from schema
- Use script:
Analyzing Postman Collections
Parse Collection
- Use script:
scripts/analyze-postman.py <collection.json> - Extracts: requests, parameters, headers, auth requirements
- Use script:
Map to MCP Tools
- Use script:
scripts/map-to-mcp-tools.py <collection.json> --output=tools.json - Creates: MCP tool definitions with parameter mapping
- Use script:
Available Scripts
scripts/analyze-openapi.py- Parse OpenAPI specs (v2, v3)scripts/analyze-postman.py- Parse Postman collectionsscripts/generate-tool-signatures.py- Generate function signaturesscripts/map-to-mcp-tools.py- Map API endpoints to MCP toolsscripts/extract-schemas.sh- Extract request/response schemas
Examples
Example 1: Analyze OpenAPI Spec
# Extract all endpoints and parameters
./scripts/analyze-openapi.py api-spec.json
# Generate Python tool signatures
./scripts/generate-tool-signatures.py api-spec.json --lang=python
Example 2: Map Postman to MCP
# Analyze Postman collection
./scripts/analyze-postman.py my-api.json
# Generate MCP tool mappings
./scripts/map-to-mcp-tools.py my-api.json --output=mcp-tools.json
Requirements
- Python 3.7+ with
pyyaml,jsonschemapackages - Valid OpenAPI v2/v3 spec or Postman collection
- jq for JSON processing
Success Criteria
- ✅ Schema parsed successfully
- ✅ All endpoints extracted with full details
- ✅ Parameter types correctly identified
- ✅ Tool signatures generated with proper types