MCP Coder
What is MCP Coder?
MCP coder enhances source code with a structured development process that turns GitHub issues into working code automatically. AI supported discussions allow to specify and review the relevant items of the specification, implementation plan and resulting code. Code quality is also ensured by rigorous usage of classical code quality assurance.
The Complete Development Workflow:
- Interactive Planning: Human-guided requirement analysis and architectural decisions using AI-powered discussions
- Automated Implementation: Full feature development with integrated testing, code quality checks, and git operations
- Quality Assurance: Built-in pylint, pytest, and mypy validation ensures production-ready code
- Intelligent Orchestration: Process automation across multiple repositories with Jenkins integration
MCP Coder combines the efficiency of AI automation with the reliability of human oversight, creating a development experience that's both faster and more robust than traditional approaches.
🎯 Vision & Architecture
MCP Coder implements a structured 3-layer development approach that separates human decision-making from AI implementation:
Three-Layer Architecture
┌─────────────────────────────────────────────────────────────────────────┐
│ 🤖 Process Automation │
│ mcp-coder coordinate command • Jenkins scheduling │
└─────────────────────────────┬───────────────────────────────────────────┘
│
│ orchestrates
│ │
▼ ▼
┌─────────────────────────────────────────┐ ┌─────────────────────────────────────────┐
│ 👤 Human Input & LLM Facilitated │ │ 🤖 LLM Work │
│ Discussions │ │ (MCP-supported) │
├─────────────────────────────────────────┤ ├─────────────────────────────────────────┤
│ • Issue analysis │ │ • Implementation planning │
│ • Implementation planning │ │ • Implementation (code writing & │
│ • Code reviews │ │ automated testing) │
│ │ │ • Complex project support (multiple │
│ │ │ steps & sessions) │
│ │ │ • Pull request generation │
│ │ │ │
│ Using Claude Code or │ │ calls │
│ Copilot CLI interactively │ │ ▼ │
│ │ │ ┌─────────────────┐ │
│ │ │ │ MCP Servers │ │
│ │ │ │ • tools-py │ │
│ │ │ │ • workspace │ │
│ │ │ └─────────────────┘ │
└─────────────────────────────────────────┘ └─────────────────────────────────────────┘
│ │
└───────────────────────────┬───────────────────────────┘
▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 📂 GitHub Foundation │
│ Source code repositories • Issue tracking with status labels │
└─────────────────────────────────────────────────────────────────────────┘
Alternative View: Mermaid Diagram
flowchart TD
PA["🤖 Process Automation<br/>mcp-coder coordinate command<br/>Jenkins scheduling"]
HI["👤 Human Input & LLM Facilitated<br/>Discussions<br/><br/>• Issue analysis<br/>• Implementation planning<br/>• Code reviews<br/><br/>Using Claude Code or<br/>Copilot CLI interactively"]
LW["🤖 LLM Work<br/>(MCP-supported)<br/><br/>• Implementation planning<br/>• Implementation (code writing &<br/> automated testing)<br/> (multiple steps & sessions)<br/>• Pull request generation"]
MCP["MCP Servers<br/>• tools-py<br/>• workspace"]
GH["📂 GitHub Foundation<br/>Source code repositories<br/>Issue tracking with status labels"]
PA -.->|orchestrates| LW
PA --> HI
PA --> LW
LW -->|calls| MCP
HI --> GH
LW --> GH
classDef automation fill:#e1f5fe,stroke:#0277bd,stroke-width:2px
classDef human fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef llm fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef foundation fill:#fff3e0,stroke:#f57c00,stroke-width:2px
classDef mcp fill:#fce4ec,stroke:#c2185b,stroke-width:2px
class PA automation
class HI human
class LW llm
class GH foundation
class MCP mcp
Key Separation of Concerns:
- 🤖 Automated LLM Work: Automated implementation calling specialized MCP servers for reliable code operations
- 🤖 Process Automation:
mcp-coder coordinatecommand orchestrates LLM work, with Jenkins scheduling for mass execution - 👤 Human Input & LLM Discussions: Issue analysis, implementation planning and code review based on LLM-based analysis and interactive discussion using Claude Code or Copilot CLI
- 📂 Foundation: GitHub: Centralized source code storage and issue management with status labels
✨ Current Features
🤖 Development Automation
- Integrated LLMs: Claude Code CLI, GitHub Copilot CLI, and LangChain backends (OpenAI, Azure OpenAI, Gemini, Anthropic API, Ollama)
- Automated Implementation: Complete feature development via
mcp-coder implement
🔄 Interactive Planning & Quality Assurance
- AI-Driven Feature Planning: Automated analysis and planning from GitHub issues
- Test-Driven Development: Automated TDD with test-first development workflows
- Comprehensive Quality Gates: Integration with pylint, pytest, and mypy via MCP servers
- Human-AI Collaboration: Structured discussion prompts for requirement refinement
🚀 Automated Workflows & GitHub Status Tracking
- GitHub Integration: Automated issue labeling, status progression, and PR management
- Git Operations: Automated branch creation, staging, committing, pushing, and rebasing
- Compact diff (
mcp-coder git-tool compact-diff): reduces large refactoring diffs for LLM review by replacing moved code blocks with summary comments - Workflow Orchestration: Automated coordination using
mcp-coder coordinate, using issue status tracking and calling Jenkins - Mass Execution: Jenkins integration enables orchestrated automated software development across issues and repositories
- Separation of Concerns: Distinct automation layer separate from human discussions
- Status Tracking: Development status progression through GitHub issue labels
🚀 Getting Started
Prerequisites
- LLM CLI (at least one): Claude Code CLI or GitHub Copilot CLI
- Python 3.11+
- Git (for repository operations)
- Code base hosted on GitHub
Installation
git clone https://github.com/MarcusJellinghaus/mcp_coder.git
cd mcp_coder
pip install -e ".[dev]"
Optional features
mcp-coder publishes several pip extras for optional integrations (LangChain providers, MLflow logging, Textual dev tooling, …). See Optional Dependencies for the full list and when to install each.
📚 Documentation
Full Documentation Index - Complete list of all documentation
Quick Links
- CLI Reference - Complete command documentation and usage examples
- Repository Setup - GitHub Actions, labels, and repository configuration
- Configuration Guide - User config files, environment variables, and platform setup
- Development Process - Detailed methodology and workflow documentation
🔗 Related Projects
- mcp-tools-py - Code quality MCP server
- mcp-workspace - File system MCP server
Built with ❤️ and AI by Marcus Jellinghaus
Metadata
Release files for mcp-coder 0.1.20
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_coder-0.1.20.tar.gz | 1.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_coder-0.1.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / mcp_coder-0.1.20.tar.gz
| Download URL | mcp_coder-0.1.20.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
741dbf00febd8d10ebf686dfbbd7928a571ef4c4032cd27d5b7ccd0af570ed5b
|
|
BLAKE2b-256 checksum How to use checksums |
dc6b582389e6ccef730efcf436661b17e0037828c87b9b46f83c0a8a7d3a32b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / mcp_coder-0.1.20-py3-none-any.whl
| Download URL | mcp_coder-0.1.20-py3-none-any.whl |
|---|---|
| Size | 423.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9acc4142f71ba670cecf7486a35278e874a7ffaa089cf25eb2ef3cb736e5a0da
|
|
BLAKE2b-256 checksum How to use checksums |
90afc0f346ba5a57b23bd23547fe79aa4c8229a8c81340c3387b5a6884a5ddf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency log