Analyze Codebase for MCP

Scan codebase to discover functions, REST endpoints, CLI commands, data access patterns. Good candidates for MCP tool exposure. Produce structured tool specification document.

When Use

• Planning MCP server for existing project, need to know what to expose
• Auditing codebase before wrapping as AI-accessible tool surface
• Comparing what codebase can do versus what already exposed via MCP
• Generating tool specification document to hand off to scaffold-mcp-server
• Evaluating whether third-party library worth wrapping as MCP tools

Inputs

• Required: Path to codebase root directory
• Required: Target language(s) of codebase (e.g., TypeScript, Python, R, Go)
• Optional: Existing MCP server code to compare against (gap analysis)
• Optional: Domain focus (e.g., "data analysis", "file operations", "API integration")
• Optional: Maximum number of tools to recommend (default: 20)