mcp -analyzer

This MCP server provides comprehensive Python code analysis by combining RUFF for linting and VULTURE for dead code detection. It exposes a set of analysis tools that can be orchestrated through the MCP framework, enabling AI assistants, IDEs, or automation to request linting, formatting, and dead code checks as part of a larger code quality workflow. Users can connect to the analyzer via UV (recommended) or through Docker, and then issue commands like ruff-check, ruff-format, vulture-scan, and analyze-code to obtain actionable feedback on Python projects. When integrated with an editor or IDE, the server can surface linting results, unused imports, and potential dead code alongside your code in real time.

Prerequisites:

• Python 3.10 or newer
• uv (recommended) or pip
• Docker (optional, for container usage)

1. Quick install with uvx (recommended):

uvx install mcp-server-analyzer

2. Install via pip:

pip install mcp-server-analyzer

3. Run with Docker (example):

docker run ghcr.io/anselmoo/mcp-server-analyzer:latest

4. Run from source (clone and install dev dependencies):

git clone https://github.com/anselmoo/mcp-server-analyzer.git
cd mcp-server-analyzer
uv sync --dev
uv run mcp-server-analyzer

5. Optional: verify installation and run tests (if you clone the repo):

uv run pytest tests/ -v

Tips and notes:

• uvx is recommended for running the MCP server; it provides streamlined development workflows. If you use uvx, the server name to reference in MCP configurations is typically mcp-server-analyzer.
• Docker images are multi-architecture and signed; prefer the ghcr.io/anselmoo/mcp-server-analyzer image for container-based setups.
• Environment variables: none are mandatory by default, but you can surface configuration options through your MCP client if the server exposes runtime flags (check the project docs for any experimental features).
• If you encounter linting or dead code detection issues, ensure your Python environment matches the project’s requirements (Python 3.10+ and compatible dependencies). Running uv sync --dev will install development dependencies used by the analyzer.
• The server exposes tools like ruff-check, ruff-format, ruff-check-ci, vulture-scan, and analyze-code to perform targeted or combined analyses. These can be invoked individually or as part of a broader analysis workflow.