Skip to main content
Glama
ToolchainConductor MCP

ToolchainConductor MCP

ToolchainConductor MCP (Lite Edition)

License: MIT Protocol: MCP Python: >=3.10

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.


Related MCP server: Build Runner MCP Server

✨ 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

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:

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

3. CLI Inspection

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)


πŸ“„ License

MIT Β© 2026 Johann Schiffer

Available Tools

4 tools
detect_toolchainsB

Inspect all installed compilers on the host (rustc, cargo, python, gcc, clang, node, go).

Inputs: no named parameters.

get_toolchain_statusA

Get quick summary of compiler readiness and supported target architectures.

Inputs: no named parameters.

parse_compiler_errorsA

Extract clean, structured JSON diagnostics (file, line, col, code, message) from raw compiler output.

Inputs: output (required).

run_isolated_buildB

Execute build command in isolated environment and return exit code, output, and parsed diagnostics.

Inputs: command (required), cwd, timeout_sec.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers