MCP Dev Servers

Give Claude Code 87 tools that turn natural-language asks into real `git`, `gh`, `dotnet`, `cargo`, `uv`, and Ollama operations. Six MCP servers, one pip install, opt in per project — so "what changed since main?" becomes a structured diff and "are any NuGet packages vulnerable?" becomes a real audit.

You: what changed since main?
Claude calls: git_diff_summary(base="main")
Returns:      { "files_changed": 3, "insertions": 47, "deletions": 12, ... }
Claude:       "You changed 3 files since main: src/auth.py (+40 −5), tests/...

✅ For: Claude Code users on Windows / macOS / Linux working in git-backed projects (any language; .NET, Rust, and Ollama get bonus tooling).

Built with FastMCP and the Model Context Protocol.

Servers

Prerequisites

Each server has its own external dependencies:

All servers require Python 3.11+.

Quick Start

Install directly from the GitHub repo (PyPI publishing is planned but not yet done — see Roadmap):

pip install "mcp-dev-servers[ollama] @ git+https://github.com/dagonet/mcp-dev-servers.git"

Once this package is on PyPI, the shorter form will also work:

pip install "mcp-dev-servers[ollama]"   # future — not yet published

Available extras: ollama (pulls httpx), git, github, dotnet, rust, python-tools, dev (for running tests). The non-ollama extras pull no Python packages today — they exist as documentation for which external tool each server expects (see Prerequisites).

The package installs 6 console scripts (mcp-git-tools, mcp-github-tools, mcp-dotnet-tools, mcp-ollama-tools, mcp-rust-tools, mcp-python-tools). Register them with claude mcp add:

# git-tools (user-level — works in every git repo)
claude mcp add --scope user --transport stdio git-tools -- mcp-git-tools

# github-tools (user-level)
claude mcp add --scope user --transport stdio github-tools \
  -e GH_PROMPT_DISABLED=1 \
  -- mcp-github-tools

# ollama-tools (user-level — if running Ollama)
claude mcp add --scope user --transport stdio ollama-tools \
  -e OLLAMA_URL=http://127.0.0.1:11434 \
  -e OLLAMA_MODEL_FIRST_PASS=mistral:7b-instruct-q4_K_M \
  -e OLLAMA_MODEL_EXTRACT_JSON=qwen2.5:7b-instruct-q4_K_M \
  -- mcp-ollama-tools

# rust-tools (user-level — works in every Rust project)
claude mcp add --scope user --transport stdio rust-tools -- mcp-rust-tools

# dotnet-tools (project-level — only in .NET projects)
claude mcp add --scope project --transport stdio dotnet-tools -- mcp-dotnet-tools


# python-tools (user-level — works in every Python project)
claude mcp add --scope user --transport stdio python-tools -- mcp-python-tools

If mcp-git-tools isn't found on your PATH, install with pipx so the scripts land in a PATH-resolvable location:

>

``bash pipx install "mcp-dev-servers[ollama] @ git+https://github.com/dagonet/mcp-dev-servers.git" ``

>

Alternatively, pass the absolute path to each console script in your claude mcp add commands.

Then grant tool permissions in your settings.json (user or project level):

{
  "permissions": {
    "allow": [
      "mcp__git-tools__*",
      "mcp__github-tools__*",
      "mcp__dotnet-tools__*",
      "mcp__ollama-tools__*",
      "mcp__rust-tools__*",
      "mcp__python-tools__*"
    ]
  }
}

Registration Strategy

Environment Variables

Tool Reference

git-tools (34 tools)

github-tools (17 tools)

dotnet-tools (19 tools)

ollama-tools (6 tools)

python-tools (7 tools)

rust-tools (4 tools)

JSON Configuration

As an alternative to claude mcp add, you can configure servers directly in ~/.claude.json (user-level) or .claude/mcp.json (project-level):

{
  "mcpServers": {
    "git-tools": {
      "command": "mcp-git-tools"
    },
    "github-tools": {
      "command": "mcp-github-tools",
      "env": {
        "GH_PROMPT_DISABLED": "1"
      }
    },
    "dotnet-tools": {
      "command": "mcp-dotnet-tools"
    },
    "rust-tools": {
      "command": "mcp-rust-tools"
    },
    "ollama-tools": {
      "command": "mcp-ollama-tools",
      "env": {
        "OLLAMA_URL": "http://127.0.0.1:11434"
      }
    },
    "python-tools": {
      "command": "mcp-python-tools"
    }
  }
}

If mcp-* scripts aren't on your PATH, use the absolute path to the script (e.g. "command": "/full/path/to/venv/bin/mcp-git-tools") or switch to pipx which installs scripts in a PATH-resolvable location.

Design Decisions

• stdio transport: All servers use stdio for Claude Code compatibility
• Cross-platform: Windows CREATE_NO_WINDOW flag prevents console popups; Unix process group handling for clean timeouts
• No bash git: git_mcp.py resolves git.exe directly to avoid .cmd wrapper issues on Windows
• English locale: dotnet-tools forces DOTNET_CLI_UI_LANGUAGE=en for consistent output parsing
• Output limits: Large outputs (diffs, logs) are truncated to prevent context overflow

Roadmap

• PyPI publishing. The package is fully PyPI-ready (pyproject.toml, hatchling build, console scripts, smoke tests) but not yet uploaded. Once published, pip install "mcp-dev-servers[ollama]" will work without the git URL.
• GitHub Actions. Automated test runs on PRs and Trusted-Publishing-based releases on tag push are planned.

Development

To contribute or run from source:

git clone https://github.com/dagonet/mcp-dev-servers.git
cd mcp-dev-servers
python -m venv .venv
.venv/Scripts/activate      # Windows
# source .venv/bin/activate  # Linux/macOS
pip install -e ".[ollama,dev]"
pytest tests/

pip install -e installs the package in editable mode, so the console scripts (mcp-git-tools, etc.) pick up your local edits immediately. pytest tests/ runs the smoke tests that verify each server imports cleanly and registers the expected number of tools.

Related Projects

Part of an ecosystem for AI-assisted development with Claude Code:

Looking for `template-sync-tools`? It moved to claude-code-toolkit in that project's v4.0.0 and ships from its server/ directory — the templates, the sync skill and the server now version together. It was removed here in 0.4.0; the last release of this package that carries it is 0.3.9, which is also the rollback target.

• claude-code-toolkit -- Template system for bootstrapping projects with Claude Code configuration, MCP server setup, and cross-platform setup scripts
• open-brain -- A personal AI memory system with a CLI, MCP server, and web dashboard; as of v0.3.0 it also compiles topic-level wiki pages with provenance and runs a contradiction-audit pass over your captured notes

Open Brain's MCP server runs alongside the servers here in the same Claude Code session -- its thoughts_*, wiki_*, and contradictions_* tools surface decisions, insights, and topic summaries that complement the git_*, gh_*, dotnet_*, cargo_*, ollama_*, and template_* tools above.