Which Python versions does python_lint_checker support?

python_lint_checker works with Python 3.6 and above. It performs static analysis without executing the file, so the version of Python on your machine doesn't affect results.

Does it require pylint, flake8, or any external linter installed?

No. python_lint_checker has zero external dependencies — it uses Python's built-in ast module and its own rule engine. Nothing needs to be installed separately.

Can I run it on an entire directory instead of a single file?

The tool currently accepts a single file path. To lint a directory, ask your AI agent to iterate over all .py files and call python_lint_checker for each one.

What's the difference between ERROR and WARNING severity?

ERROR means the code has a definite problem — a syntax error, undefined variable, or logic bug that will cause incorrect behavior. WARNING flags code quality issues that should be fixed but won't necessarily break execution.

How does this compare to running pylint or ruff directly?

python_lint_checker is designed for MCP — it returns structured JSON that your AI agent can parse and act on. For standalone CLI linting, pylint or ruff will give you more rules and configurability. This tool's value is its zero-setup integration into any MCP-compatible AI workflow.

docs/tools/python_lint_checker

AgenticCode

Python Code Linter MCP Tool

CLI Tool Name: python_lint_checker

Static analysis for Python files. Detects syntax errors, unused imports, style violations, and complexity issues. Runs entirely on your machine — zero external dependencies, zero network calls.

Parameters

Parameter	Type	Required	Description
file_path	string	yes	Absolute or relative path to the Python file to analyze.

What it checks

Syntax errors

Invalid Python syntax that prevents execution.

Unused imports

Imported modules and symbols that are never used.

Undefined variables

References to names that are not defined in scope.

Line length

Lines exceeding PEP 8's 79-character limit.

Complexity

Functions and methods with high cyclomatic complexity.

Style violations

PEP 8 formatting issues — spacing, naming, indentation.

Severity levels

ERROR

Must fix. These prevent correct execution or indicate definite bugs.

WARNING

Should fix. Code quality issues that may cause problems.

INFO

Optional. Style suggestions that improve readability.

Example output

json

{
  "file": "src/utils.py",
  "findings": [
    {
      "line": 14,
      "severity": "ERROR",
      "code": "E0001",
      "message": "SyntaxError: invalid syntax"
    },
    {
      "line": 42,
      "severity": "WARNING",
      "code": "W0611",
      "message": "Unused import: os"
    },
    {
      "line": 67,
      "severity": "WARNING",
      "code": "C0301",
      "message": "Line too long (92 > 79 characters)"
    }
  ],
  "summary": {
    "errors": 1,
    "warnings": 2,
    "info": 0
  }
}

How to use it

Your AI client calls this tool automatically when configured. You can also prompt your assistant directly:

example prompt

Check src/main.py for any lint errors or code quality issues.

[tip]

Add python_lint_checker to your Claude Code hooks to automatically lint every Python file you write or edit — no prompting required.

Explore other AgenticStore MCP tools

→ Secret & Repo Scanner MCP Tool → Dependency Vulnerability Scanner MCP Tool → Web Search & Scraper MCP Tool

← overview repo_scanner →

Frequently asked questions