M
MarcusJellinghaus/mcp-tools-py
MCP server providing code quality checks (pylint and pytest) with smart LLM-friendly prompts for analysis and…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"marcusjellinghaus-mcp-tools-py": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}解析自我们于 2026-10-29 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"marcusjellinghaus-mcp-tools-py": {
"command": "npx",
"args": ["@modelcontextprotocol/inspector"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio marcusjellinghaus-mcp-tools-py -- npx @modelcontextprotocol/inspector
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 21 ★ · MarcusJellinghaus/mcp-tools-py · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-10-30 · 最近见到 2026-11-14 · 共见到 16 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 21 ★ · 1 个来源 · repo
- 安装
npx @modelcontextprotocol/inspector
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx @modelcontextprotocol/inspector。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
MarcusJellinghaus/mcp-tools-py；我们收录于 2026-10-30；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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 |
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/marcusjellinghaus-mcp-tools-py/)
- 来源
- github · https://github.com/MarcusJellinghaus/mcp-tools-py
- 按领域浏览
- MCP 服务
- Traction
- 21 ★
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。