Skip to main content
Glama

Related Servers

Alternatives to LocalForge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Local-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.
      13
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Secure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives MCP-compatible AI clients safe, hands-on access to local codebases: file reading/search, multi-file patches, command execution, interactive sessions, Git inspection, and coordination of local agent providers such as Antigravity and OpenCode.
      18
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives any MCP-compatible AI chat or agent a safe, model-neutral coding runtime with file read/search, structured multi-file patches, command execution, interactive sessions, and git operations, all confined to a single workspace and gated by permission modes.
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets, but shell, run_python, and validate all execute commands and can be confused; project_context also partially overlaps git_status by returning Git state. The descriptions do help separate their intended uses, so ambiguity is limited.

    Naming Consistency4/5

    Nearly all tools use snake_case with clear domain prefixes such as git_, process_, and work_, making the set predictable. Minor deviations include noun-first forms like git_status/work_update and the lone validate, but naming remains readable and consistent overall.

    Tool Count4/5

    At 16 tools, the server is slightly above the ideal 3-15 range but still well-scoped for a local development/code-agent environment. File, execution, process, Git, handoff, and validation capabilities each justify their place without obvious filler.

    Completeness4/5

    The surface covers file listing/reading/searching/editing, command execution, process status/stopping, Git inspection, work handoff, and validation. Minor gaps exist around Git write operations (commit/push) and explicit process start/list, but most workflows can be completed through shell or apply_patch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues