Skip to main content
Glama
johannschiffer

ToolchainConductor MCP

README.md
# ToolchainConductor MCP (Lite Edition)

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
[![Protocol: MCP](https://img.shields.io/badge/MCP-2024--11--05-green.svg)](https://modelcontextprotocol.io/)
[![Python: >=3.10](https://img.shields.io/badge/Python->=3.10-yellow.svg)](https://python.org/)

**ToolchainConductor MCP** is a polyglot compiler conductor, build runner, and diagnostic parsing sidecar designed for autonomous AI coding agents (Claude Desktop, Cursor, OpenAI Codex, LangGraph).

It enables agents to build hybrid polyglot projects (Python, Rust, Node, C/C++, Go), parse noisy compiler outputs into clean, structured JSON diagnostics, and eliminate ANSI escape code bloat from LLM context windows.

---

## ๐ŸŽฏ The Problem

When autonomous AI agents build multi-language or compiled code:
1. **ANSI Compiler Noise:** Compilers dump hundreds of lines of colored ANSI escape sequences that pollute LLM context windows without providing structured error coordinates.
2. **Missing Compilers & Incompatible Toolchains:** Agents attempt to run `cargo` or `gcc` blindly without detecting installed host toolchains and target architectures.
3. **Redundant Re-compilations:** Without intermediate artifact caching, agents recompile heavy dependencies repeatedly, exhausting turn limits and CPU quotas.

**ToolchainConductor** solves this by providing a clean, protocol-native build orchestrator.

---

## โœจ Features (Lite Edition)

- ๐Ÿ” **Host Toolchain Discovery:** Automatic inspection of installed compilers (`rustc`, `cargo`, `python3`, `gcc`, `clang`, `node`, `go`).
- ๐Ÿงน **Compiler Diagnostic Parser:** Strips ANSI escape sequences and extracts structured JSON errors (`file`, `line`, `col`, `code`, `message`) for Rust, GCC/Clang, and Python.
- โšก **Isolated Build Runner:** Executes commands in clean child environments with timeout enforcement.
- ๐Ÿ“ฆ **Zero External Dependencies:** Pure Python standard library implementation.

---

## ๐Ÿš€ Quickstart

### 1. Installation

```bash
git clone https://github.com/johannschiffer/toolchainconductor-mcp.git
cd toolchainconductor-mcp
pip install -e .
```

### 2. Configure in Claude Desktop or Cursor

Add to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "toolchainconductor": {
      "command": "toolchainconductor",
      "args": ["run"]
    }
  }
}
```

### 3. CLI Inspection

```bash
toolchainconductor detect
```

---

## ๐Ÿ› ๏ธ MCP Tools Reference

| Tool | Parameters | Description |
|---|---|---|
| `detect_toolchains` | *(none)* | Inspects all installed compilers and versions on host |
| `parse_compiler_errors` | `output` | Transforms raw compiler logs into structured JSON diagnostics |
| `run_isolated_build` | `command`, `cwd`, `timeout_sec` | Executes build command in clean environment |
| `get_toolchain_status` | *(none)* | Returns compiler readiness report |

---

## ๐Ÿš€ Upgrade to ToolchainConductor Pro

Need content-addressable build caching, memory safety audits, and automated PyO3 / FFI scaffolding?

The **ToolchainConductor Pro Edition** adds:
- โšก **Deterministic Build Cache (SQLite WAL):** Deduplicates compiled artifacts via SHA-256 source and lockfile hashes, skipping redundant builds.
- ๐Ÿ›ก๏ธ **Memory-Safety & Linter Hardening:** Automatic invocation of `cargo audit`, `cargo clippy`, and sanitizers with structured auto-repair recipes.
- ๐Ÿ”— **Polyglot FFI Scaffolder:** Generates production-ready PyO3 (Python-Rust) and CFFI bridge boilerplate.
- ๐Ÿณ **Production Docker & Docker Compose multi-stage manifests.**
- ๐Ÿงช **100% Passing Pytest Suite.**

๐Ÿ‘‰ **[Get ToolchainConductor Pro on Gumroad ($14.99 USD)](https://johanld.gumroad.com/)**

---

## ๐Ÿ“„ License

MIT ยฉ 2026 [Johann Schiffer](https://github.com/johannschiffer)

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation3/5

detect_toolchains and get_toolchain_status overlap significantly, both reporting compiler availability and readiness. run_isolated_build also returns parsed diagnostics, making parse_compiler_errors partly redundant when used together, though each tool has a distinguishable core purpose.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (detect_toolchains, parse_compiler_errors, run_isolated_build, get_toolchain_status). There are no deviations in style or convention.

Tool Count5/5

Four tools is well-scoped for a focused toolchain inspection and build-execution server. Each tool covers a distinct stage (detect, parse, run, status), though there is some functional overlap between detect and status.

Completeness4/5

The surface covers the core lifecycle of detecting toolchains, running isolated builds, parsing errors, and summarizing status. Minor gaps exist around installing or switching toolchains and managing build artifacts, but core workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues