MCP Code Checker MCP Server

MCP server providing code quality checks (pylint and pytest) with smart LLM-friendly prompts for analysis and fixes. Enables Claude and other AI

Local serverstdioPython

What is the MCP Code Checker MCP server?

If you already use MCP Code Checker, the mcp code checker mcp server is the piece that lets your assistant work with it directly. MCP server providing code quality checks (pylint and pytest) with smart LLM-friendly prompts for analysis and fixes. Enables Claude and other AI assistants to analyze your code and suggest improvements.

What the server does

A Model Context Protocol (MCP) server providing code quality checking operations with easy client configuration. This server offers an API for performing code quality checks within a specified project directory, following the MCP protocol design.

This MCP server enables AI assistants like Claude (via Claude Desktop), VSCode with GitHub Copilot, or other MCP-compatible clients to run code quality checks on Python projects. The tools provided are:

  • run_pylint_check: Run pylint on the project code and generate smart prompts for LLMs
  • run_pytest_check: Run pytest on the project code and generate smart prompts for LLMs
  • run_mypy_check: Run mypy type checking on the project code

Installation

Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Notes — The Notes tool exposed by this server
  • Troubleshooting — The Troubleshooting tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: PYTHONPATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Code Checker's toolset — Notes, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by MarcusJellinghaus; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
NotesThe Notes tool exposed by this server.
TroubleshootingThe Troubleshooting tool exposed by this server.

How to install the MCP Code Checker MCP server

{
    "mcpServers": {
        "mcp-tools-py": {
            "command": "mcp-tools-py",
            "args": [
                "--project-dir", "/path/to/your/project",
                "--venv-path", "${VIRTUAL_ENV}"
            ]
        }
    }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PYTHONPATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use MCP Code Checker to Notes.
  • Use MCP Code Checker to Troubleshooting.

Frequently asked questions

MCP Code Checker provides a more focused, secure approach: only pylint, pytest, and mypy can be executed, all operations are scoped to the specified `project_dir`, and results are formatted and size-limited to reduce context load. The server also logs every tool call with parameters, timing, and results.