Skip to main content
Glama
Violetylove

gitbash-mcp

by Violetylove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to gitbash-mcp

No user-submitted related servers found.

    Related Servers

    • bash-mcp

      jesusignaciob
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes WSL bash as a structured tool to MiniMax Code, returning stdout, stderr, exit code, duration, and classification from a single call. Adds command safety classification, audit logging with rotation, concurrency limits, and binary discovery for agents running shell commands.
      MIT

    • Smart Assistant MCP

      mehdisafer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely work on Windows developer workstations through governed, project-scoped filesystem access, durable command execution, bounded search, Windows operations, and resource-aware runtime controls. It also supports optional developer-context backends for code navigation, repository graph exploration, and memory retrieval.
      Apache 2.0

    • @akms/mcp-wsl

      juncha9
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI agent to run shell commands and move files inside a WSL distro on the same Windows machine via wsl.exe, with no sshd, key, or port required. Each pre-registered distro-and-user entry enforces guard policies limiting dangerous commands, Windows interop, write targets, and accessible paths.
      10
      1
      MIT

    • just-bash-mcp

      drizjet
      A
      license
      A
      quality
      D
      maintenance
      Sandboxed bash execution MCP server for AI agents, using an in-memory virtual filesystem overlay to prevent real filesystem damage, with configurable network access, timeouts, and optional Python/JS runtimes.
      9
      62 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    exec is clearly the action tool, while bash_info, doctor, and policy are distinct diagnostic/info tools. bash_info and doctor overlap somewhat (both report bash path and versions), but the descriptions specify that bash_info is a quick summary and doctor is a full diagnosis with fix steps.

    Naming Consistency3/5

    The set mixes a verb-style name (exec) with noun-style names (bash_info, doctor, policy), so there is no single predictable verb_noun pattern. Names are still short, readable, and unambiguous, but the convention is not consistent.

    Tool Count4/5

    Four tools is lean but well-scoped for a shell bridge: one execution tool plus three focused diagnostics. It is slightly thin (no separate audit-log or process-listing tool), but each tool earns its place.

    Completeness4/5

    exec covers the core domain (running bash/git commands with output capture, exit codes, policy enforcement), and the diagnostics cover setup, environment, and policy questions. Minor gaps remain, such as no dedicated tool to read the audit log or inspect queued/running commands (those exist only as external CLI/status fields).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources