Skip to main content
Glama
egn88

Build Runner MCP Server

by egn88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Build Runner MCP Server

No user-submitted related servers found.

    Related Servers

    • ToolchainConductor MCP

      johannschiffer
      A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to discover installed host compilers, execute builds in isolated child environments with timeout enforcement, and convert noisy ANSI-laden compiler logs from Python, Rust, C/C++, Node, and Go toolchains into clean structured JSON diagnostics. It also reports toolchain readiness so agents can avoid blind invocations of missing compilers.
      4
      MIT

    • MCP Build Environment Service

      jbroll
      A
      license
      A
      quality
      D
      maintenance
      Provides secure access to containerized build environments for software projects, enabling AI assistants to execute builds, run tests, manage git operations, and inspect build artifacts without requiring local installation of dependencies.
      6
      MIT

    • Build MCP Server

      TeodorTrotea
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage development workflows by running build commands, executing tests, analyzing package.json files, installing dependencies, and performing code linting. Supports multiple package managers (npm, yarn, pnpm) and provides detailed error reporting for development operations.
      5
      MIT

    • Pare

      Hughes74053
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to invoke common developer tools — git, GitHub, npm, Python, cargo, Docker, Kubernetes, linters, and test runners — and receive schema-validated structured JSON instead of raw terminal text. This removes brittle string parsing and cuts token usage dramatically on verbose commands like builds, installs, and test runs.
      0
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools cleanly separate by ecosystem and build phase: Java build/install/compile/test versus Node build/test/typecheck. The only real ambiguity is compile_project vs build_project, since compilation is normally part of a build, but the descriptions clarify that compile focuses on diagnostics while build produces artifacts.

    Naming Consistency3/5

    Naming is mixed: Java tools mostly follow verb_project (build_project, install_project, compile_project), while Node tools follow node_verb (node_test, node_build, node_typecheck). run_tests breaks the Java pattern by using a generic verb instead of something like test_project, and set_java_version follows yet another style.

    Tool Count5/5

    Nine tools is well-scoped for a multi-language build runner. Each tool covers a meaningful build, test, install, detect, or environment-management action without feeling padded or redundant.

    Completeness4/5

    The surface covers the core Java and Node.js workflows: detection, building, compiling, testing, installing for Java, and type checking for TypeScript projects. Minor gaps like a Node install/publish command or a generic clean task are absent, but agents can still complete typical build-and-test workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources