ToolchainConductor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect_toolchainsB | Inspect all installed compilers on the host (rustc, cargo, python, gcc, clang, node, go). |
| parse_compiler_errorsA | Extract clean, structured JSON diagnostics (file, line, col, code, message) from raw compiler output. |
| run_isolated_buildB | Execute build command in isolated environment and return exit code, output, and parsed diagnostics. |
| get_toolchain_statusA | Get quick summary of compiler readiness and supported target architectures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
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.
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.
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.
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.