Skip to main content
Glama
jbroll

MCP Build Environment Service

by jbroll

Related Servers

Alternatives to MCP Build Environment Service

No user-submitted related servers found.

    Related Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to automatically analyze GitHub repositories and set up development environments by detecting tech stacks, installing dependencies, and verifying project builds. Provides safe tools for repository cloning, file system operations, package installation, and build verification through an allowlisted command system.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.
      15
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute code, run tests, and build projects inside disposable Docker sandboxes, protecting the host machine through enforced isolation, filesystem snapshots, and network controls.
      15
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely run commands, install dependencies, test, and modify code inside disposable, policy-enforced Docker sandboxes isolated from the host, returning results and diffs.
      15
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.
      3
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes: env shows environment info, git runs git commands, list shows repositories, ls lists files, make runs make, and read_file reads file contents. However, 'list' and 'ls' could potentially be confused as both involve listing, though 'list' is for repositories and 'ls' is for files within a repository, which is clarified in descriptions.

    Naming Consistency3/5

    The naming is mixed: 'env', 'git', 'list', 'ls', 'make', and 'read_file' use a variety of styles. 'env', 'git', 'list', 'ls', and 'make' are simple command-like names, while 'read_file' uses snake_case. There's no consistent verb_noun pattern, but the names are generally readable and intuitive for their functions.

    Tool Count5/5

    With 6 tools, this is well-scoped for a build environment service. Each tool serves a clear purpose in managing repositories, files, and build processes, and the count is appropriate without being too thin or bloated for the domain.

    Completeness4/5

    The tool set covers key operations for a build environment: environment inspection (env), repository management (git, list), file operations (ls, read_file), and build execution (make). A minor gap is the lack of tools for writing or modifying files, which might be intentional for safety but could limit some build workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues