AI Distiller MCP

What janreges/ai-distiller-mcp MCP server does

janreges/ai-distiller-mcp MCP server makes the AI Distiller code-structure extractor available to MCP-compatible clients. It is intended for projects where sending the entire source tree to an AI model would exceed practical context limits or make API relationships difficult to identify.

The core operation reduces source code to a compact representation of the information an agent usually needs to use existing code: public methods, properties, types, imports, and basic documentation. The default output excludes method bodies and protected, internal, or private members. Filtering options can include those members, implementation details, comments, or other content when a broader view is required.

The repository describes support for more than 12 programming languages and provides text, Markdown, structured JSON, JSONL, and XML output formats. Distillation can target one file or a directory, and the tool can report compression and processing statistics.

How it works

The MCP interface separates browsing, extraction, and analysis-prompt generation. list_files helps an agent inspect directories and view file statistics. distill_file and distill_directory then produce reduced code context for a file or directory. get_capabilities reports available AI Distiller capabilities.

The analysis tools do not perform the underlying review themselves. Instead, they prepare prompts containing distilled code for an AI agent to process. Available workflows cover bug hunting, refactoring, Mermaid diagram generation, OWASP Top 10 security analysis, documentation, systematic file-by-file analysis, multi-file documentation, complex analysis, performance, and coding best practices. aid_analyze provides direct access to the AI actions for custom workflows.

Setup and configuration

Install the MCP package published as @janreges/ai-distiller-mcp from npm, then configure it in an MCP-compatible client. The README explicitly names Claude, Cursor, VS Code, and Windsurf as supported integration targets, and includes a Claude Desktop usage guide in its documentation structure.

No API key or external paid AI service is specified in the provided material. The generated prompts are saved to a .aid/ directory by default for workflows that create files; small codebases can instead use standard output according to the CLI behavior described by the project.

Configuration follows AI Distiller's filtering model. Public members, documentation, and imports are included by default, while implementation bodies and non-public visibility levels are excluded. Worker count, output format, comments, docstrings, and summary style can be adjusted through the underlying Distiller options.

Tools and capabilities

The MCP tool set includes:

• File and directory distillation
• Directory browsing with file statistics
• Capability discovery
• Bug-hunting and refactoring prompt generation
• Mermaid diagram prompt generation
• OWASP Top 10 security-analysis prompts
• Documentation and multi-file documentation workflows
• Deep file analysis and complex analysis workflows
• Performance and best-practice analysis prompts
• A general analysis entry point for custom actions

Limitations and notes

AI Distiller prepares context and prompts; it does not carry out the requested security review, refactoring, documentation task, or other analysis itself. An AI agent must read or execute the generated prompt content.

The project identifies this MCP release as an early version and requests feedback through GitHub discussions or issues. The supplied material does not state a license, so licensing should be verified in the repository before redistribution.