mcp-tools-py MCP工具

Required Parameters

Using as a Dependency

In requirements.txt

Add this line to your requirements.txt:

mcp-tools-py @ git+https://github.com/MarcusJellinghaus/mcp-tools-py.git

Or as an optional dependency

[project.optional-dependencies] dev = [ "mcp-tools-py @ git+https://github.com/MarcusJellinghaus/mcp-tools-py.git", ] ```

Install from requirements.txt

pip install -r requirements.txt

Or with optional dependencies

pip install ".[dev]" ```

Install dependencies

pip install -e .

Install development dependencies

pip install -e ".[dev]" ```

Installation

See INSTALL.md for detailed installation instructions.

Quick install:

```bash

Install from GitHub (recommended)

pip install git+https://github.com/MarcusJellinghaus/mcp-tools-py.git

Verify installation

mcp-tools-py --help

**Development install:**

Clone and install for development

git clone https://github.com/MarcusJellinghaus/mcp-tools-py.git cd mcp-tools-py python -m venv .venv source .venv/bin/activate # On Windows: .venv\Scripts\activate pip install -e ".[dev]" mcp-tools-py --help ```

Installation Commands

After adding to requirements.txt or pyproject.toml:

```bash

Install from pyproject.toml

pip install .

Quick MCP Client Setup

Automated Setup (Recommended)

1. First install the server:

   pip install git+https://github.com/MarcusJellinghaus/mcp-tools-py.git
   

2. Configure with mcp-config:

   mcp-config
   

   mcp-config mcp-tools-py
   

This will prompt you for your project directory and automatically configure your MCP client.

Manual Setup

If you prefer manual configuration, edit your MCP configuration file:

Claude Desktop (%APPDATA%\Claude\claude_desktop_config.json on Windows):

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

For development mode:

{
    "mcpServers": {
        "mcp-tools-py": {
            "command": "python",
            "args": [
                "-m",
                "src.main",
                "--project-dir",
                "/path/to/your/project"
            ],
            "env": {
                "PYTHONPATH": "/path/to/mcp-tools-py"
            }
        }
    }
}

VSCode (.vscode/mcp.json):

{
    "servers": {
        "mcp-tools-py": {
            "command": "mcp-tools-py",
            "args": ["--project-dir", "."]
        }
    }
}

VSCode development mode:

{
    "servers": {
        "mcp-tools-py": {
            "command": "python",
            "args": ["-m", "src.main", "--project-dir", "."],
            "env": {
                "PYTHONPATH": "/path/to/mcp-tools-py"
            }
        }
    }
}

Basic Usage

mcp-tools-py --project-dir /path/to/project [options]

Pylint Configuration

Pylint reads your project's pyproject.toml automatically. Control which issues are reported by configuring [tool.pylint.messages_control] in your pyproject.toml. See docs/pyproject-configuration.md for examples and migration guidance.

Optional Parameters

#### Python Configuration <div class="rdm-tbl-wrap"><table class="rdm-tbl"><thead><tr><th>Parameter</th><th>Type</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>--python-executable</td><td>string</td><td>sys.executable</td><td>Path to Python interpreter for running pytest, pylint, and mypy. Should point to the environment where these tools are installed (the tool's own venv), not the project's runtime venv</td></tr><tr><td>--venv-path</td><td>string</td><td>None</td><td>Path to the virtual environment where pytest, pylint, and mypy are installed. When specified, this venv's Python will be used instead of --python-executable. This should be the tool's own venv, not the project's runtime venv</td></tr></tbody></table></div>

#### Test Configuration <div class="rdm-tbl-wrap"><table class="rdm-tbl"><thead><tr><th>Parameter</th><th>Type</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>--test-folder</td><td>string</td><td>&quot;tests&quot;</td><td>Path to the test folder (relative to project-dir)</td></tr><tr><td>--keep-temp-files</td><td>flag</td><td>False</td><td>Keep temporary files after test execution. Useful for debugging when tests fail</td></tr></tbody></table></div>

#### Logging Configuration <div class="rdm-tbl-wrap"><table class="rdm-tbl"><thead><tr><th>Parameter</th><th>Type</th><th>Default</th><th>Description</th></tr></thead><tbody><tr><td>--log-level</td><td>string</td><td>&quot;INFO&quot;</td><td>Set logging level. Choices: DEBUG, INFO, WARNING, ERROR, CRITICAL</td></tr><tr><td>--log-file</td><td>string</td><td>None</td><td>Path for structured JSON logs. If not specified, logs only to console</td></tr><tr><td>--console-only</td><td>flag</td><td>False</td><td>Log only to console, ignore --log-file parameter</td></tr></tbody></table></div>

Environment Configuration

The --python-executable and --venv-path options must point to the environment where pytest, pylint, and mypy are installed — this is typically the tool's own virtual environment, not your project's runtime venv.

Correct Configuration

Point to the venv where mcp-tools-py and its tools are installed:

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

Incorrect Configuration

Do not point to your project's runtime venv if it doesn't have pytest/pylint/mypy installed:

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

This will fail if your project's .venv doesn't have the required tools installed.

MCP Client Configuration

This server can be easily configured using the mcp-config Python tool. The mcp-config tool provides:

• Interactive setup: Works with Claude Desktop and VSCode
• Configuration management: Add, remove, and view server configurations
• Server repository: Access to curated MCP server collection

Prerequisites: Install Python and the mcp-config tool.

Note: While other MCP clients like Windsurf and Cursor support MCP servers, they may require manual configuration.

Setting up the development environment

```bash

Create and activate a virtual environment

python -m venv .venv

Command Line Interface (CLI)

Using the CLI Command (Recommended)

After installation, you can run the server using the mcp-tools-py command:

mcp-tools-py --project-dir /path/to/project [options]

For a package-based structure

target_directories = ["mypackage", "tests"]

For complex multi-module projects

target_directories = ["module1", "module2", "shared", "tests"] ```

Set the PYTHONPATH and run the server module using mcp dev

set PYTHONPATH=. && mcp dev src/server.py ```

Using Python Module (Alternative)

You can also run the server as a Python module:

```bash python -m mcp_tools_py --project-dir /path/to/project [options]

Troubleshooting

• "No module named pytest" (or pylint/mypy): Your --python-executable or --venv-path points to an environment that doesn't have the required tools installed. Update the configuration to point to the correct environment.
• After installing missing tools, restart the MCP server for changes to take effect. Tool availability is checked at startup and cached for the session.