M
MarcusJellinghaus/mcp-tools-py
MCP server providing code quality checks (pylint and pytest) with smart LLM-friendly prompts for analysis and…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"marcusjellinghaus-mcp-tools-py": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}Parsed from the README we fetched on 2026-10-29; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"marcusjellinghaus-mcp-tools-py": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio marcusjellinghaus-mcp-tools-py -- npx @modelcontextprotocol/inspector
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 21 ★ · MarcusJellinghaus/mcp-tools-py · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-30 · last seen 2026-11-14 · seen 16× · listed by 1 sources
- Score
- score 103 · 21 ★ · 1 sources · repo
- Install
npx @modelcontextprotocol/inspector
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @modelcontextprotocol/inspector. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
MarcusJellinghaus/mcp-tools-py；first catalogued 2026-10-30；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# MCP Tools Py
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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.
## Overview
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, formatting and refactoring on Python projects. See Available Tools for the full list.
Scope: This server covers Python projects only. Support for other languages can be provided through separate, dedicated MCP servers with similar functionality.
Why a dedicated MCP server instead of bash access?
A general-purpose bash MCP tool allows more flexibility, but at the expense of less control. This server takes a more focused approach:
Security: Only a defined set of tools can be executed — see Available Tools. All operations are scoped to the specified projectdir.
Context management: Results are formatted and size-limited to reduce context load on the AI assistant. Output is structured as actionable prompts rather than raw tool output.
Transparency: The server is open source, and detailed structured logging records every tool call with parameters, timing, and results.
## Features
All tools are listed under Available Tools. The sections below
document the parameters of the most-used ones.
### Pylint Parameters
The pylint tools expose the following parameters for customization:
| Parameter | Type | Default | Description |
| extraargs | list | None | Optional list of additional pylint CLI arguments (e.g. ["--disable=W0611"]) |
| targetdirectories | list | None (auto-detected) | Directories to analyze relative to projectdir. Auto-detected from pyproject.toml when omitted |
| maxissues | integer | 1 | Number of issue types shown in detail; the rest are summarised as counts. 0 = counts only (per-rule count and directory split) |
### Pylint Configuration
Pylint reads your project's pyproject.toml automatically. Control which issues
are reported by configuring [tool.pylint.messagescontrol] in your pyproject.toml.
See docs/pyproject-configuration.md for examples
and migration guidance.
### Target Directory Auto-Detection
When targetdirectories is not specified, the tools that accept it (pylint, mypy, ruff
check, ruff fix, bandit, vulture, and runformatcode) auto-detect directories from
pyproject.toml:
Source dirs from [tool.setuptools.packages.find] where (fallback: ["src"])
Test dirs from [tool.pytest.inioptions] testpaths (fallback: ["tests"])
rundeptrycheck auto-detects source directories only, excluding test paths.
Only directories that exist on disk are included. You can override auto-detection
by passing an explicit list:
["src"] - Analyze only source code directory
["src", "tests"] - Analyze both source and test directories
["mypackage", "tests"] - For projects with different package structures
["."] - Analyze entire project directory (may be slow for large projects)
### Pytest Parameters
runpytestcheck exposes the following parameters for customization:
| Parameter | Type | Default | Description |
## Overview
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, formatting and refactoring on Python projects. See Available Tools for the full list.
Scope: This server covers Python projects only. Support for other languages can be provided through separate, dedicated MCP servers with similar functionality.
Why a dedicated MCP server instead of bash access?
A general-purpose bash MCP tool allows more flexibility, but at the expense of less control. This server takes a more focused approach:
Security: Only a defined set of tools can be executed — see Available Tools. All operations are scoped to the specified projectdir.
Context management: Results are formatted and size-limited to reduce context load on the AI assistant. Output is structured as actionable prompts rather than raw tool output.
Transparency: The server is open source, and detailed structured logging records every tool call with parameters, timing, and results.
## Features
All tools are listed under Available Tools. The sections below
document the parameters of the most-used ones.
### Pylint Parameters
The pylint tools expose the following parameters for customization:
| Parameter | Type | Default | Description |
| extraargs | list | None | Optional list of additional pylint CLI arguments (e.g. ["--disable=W0611"]) |
| targetdirectories | list | None (auto-detected) | Directories to analyze relative to projectdir. Auto-detected from pyproject.toml when omitted |
| maxissues | integer | 1 | Number of issue types shown in detail; the rest are summarised as counts. 0 = counts only (per-rule count and directory split) |
### Pylint Configuration
Pylint reads your project's pyproject.toml automatically. Control which issues
are reported by configuring [tool.pylint.messagescontrol] in your pyproject.toml.
See docs/pyproject-configuration.md for examples
and migration guidance.
### Target Directory Auto-Detection
When targetdirectories is not specified, the tools that accept it (pylint, mypy, ruff
check, ruff fix, bandit, vulture, and runformatcode) auto-detect directories from
pyproject.toml:
Source dirs from [tool.setuptools.packages.find] where (fallback: ["src"])
Test dirs from [tool.pytest.inioptions] testpaths (fallback: ["tests"])
rundeptrycheck auto-detects source directories only, excluding test paths.
Only directories that exist on disk are included. You can override auto-detection
by passing an explicit list:
["src"] - Analyze only source code directory
["src", "tests"] - Analyze both source and test directories
["mypackage", "tests"] - For projects with different package structures
["."] - Analyze entire project directory (may be slow for large projects)
### Pytest Parameters
runpytestcheck exposes the following parameters for customization:
| Parameter | Type | Default | Description |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/marcusjellinghaus-mcp-tools-py/)
- Source
- github · https://github.com/MarcusJellinghaus/mcp-tools-py
- Browse by field
- MCP servers
- Traction
- 21 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.