Typescript Analyzer MCP

🚀 TypeScript Analyzer MCP Server - Enterprise Edition

A high-performance MCP (Model Context Protocol) server designed to analyze and rectify TypeScript any types in codebases. It comes equipped with advanced error handling, caching, and intelligent type inference capabilities.

🚀 Quick Start

This TypeScript Analyzer MCP Server offers a range of features to streamline your TypeScript code analysis and maintenance. Follow the installation steps below to get started.

✨ Features

• 🔍 Analyze TypeScript Files: Scan files for any types and receive replacement suggestions.
• 🛠️ Fix TypeScript Files: Automatically replace any types with more specific ones.
• 📊 Batch Processing: Handle multiple files at once.
• 🧩 Component Interface Generation: Generate TypeScript interfaces for React components.
• ⚙️ Server Configuration: Dynamically update server configurations (log level, caching, etc.).
• 🔧 Cache Management: Clean and manage analysis caches.

📦 Installation

1. Clone this repository.
2. Install dependencies:

   npm install
   

3. Build the project:

   npm run build
   

4. Start the server:

   npm run start
   

   or

   node dist/index.js
   

💻 Usage Examples

Using with Claude Desktop

To use this MCP server with Claude Desktop, add it to the .claude-app.json configuration file:

{
  "mcpServers": {
    "typescript-analyzer": {
      "command": "node",
      "args": ["/path/to/typescript-analyzer-mcp/dist/index.js"],
      "env": {}
    }
  }
}

Tools

getServerInfo

Retrieve basic information about the analyzer server (name, version, description, features, configuration). Example:

Please provide server information

configureServer

Update server configurations (log level, caching, etc.) at runtime. Parameters:

• config: A partial configuration object to merge with the current configuration. Example:

Please update the log level to 'debug'

analyzeTypeScriptFile

Analyze any types in a TypeScript file. Parameters:

• filePath: The path of the TypeScript file to analyze.
• skipCache: (Optional) If true, force a fresh analysis. Example:

Please analyze the any types in the src/components/Button.tsx file

fixTypeScriptFile

Fix any types in a single TypeScript file. Parameters:

• filePath: The path of the TypeScript file to fix.
• fixType: The default replacement type (default: "unknown").
• dryRun: If true, show changes without applying them.
• skipBackup: If true, do not create a backup file before modification. Example:

Please fix the any types in the src/components/Button.tsx file, using Record<string, unknown> as the default replacement

batchFixTypeScriptFiles

Batch fix any types in multiple TypeScript files. Parameters:

• directory: The path of the file or directory to process.
• fixType: (Optional) Default: "unknown".
• dryRun: (Optional) Default: false.
• skipBackup: (Optional) Default: false. Example:

Please batch fix the any types in all TypeScript files under the src/components directory

generateTypeScriptInterface

Generate a TypeScript interface for a React component. Parameters:

• componentPath: The file path of the React component.
• outputPath: The path of the output interface file (default: a .types.ts file with the same name as the component file). Example:

Please generate a TypeScript interface for components/Button.tsx

📚 Documentation

Type Mapping

For uncovered patterns, unknown is used as the default.

📄 License

This project is licensed under the MIT License.