Skip to main content
Glama
LJLCarrien

Local Ops MCP

by LJLCarrien

Related Servers

Alternatives to Local Ops MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.
      0
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT or any MCP client to operate safely on a designated workspace by listing, reading, searching, writing, and trashing files, inspecting Git status/log/diff, and optionally running allowlisted executables without a shell.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI clients with safe, structured access to local filesystem, Git repositories, and project contexts, featuring file operations, git status/diff, project management, and built-in code review/bug analysis prompts.
      1,107 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to safely inspect and modify project files within explicitly allowed workspace roots, with controls for file operations, git status/diff, and optionally allowlisted command execution.
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT to inspect, edit, test, commit, and push code within a single constrained project directory, with gitignore-aware traversal and guarded file operations. It supports strict command allowlisting or trusted YOLO execution while confining file tools to the configured workspace root.
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool maps to a distinct filesystem or Git operation, and most names are self-explanatory. The only mild ambiguity is between move_file and rename_file, though the descriptions clearly separate moving to a new path from renaming within the same directory.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern, such as list_directory, copy_file, git_diff_staged, and git_amend_message. No mixed conventions or vague verbs appear.

    Tool Count4/5

    Eighteen tools is on the higher end, but the server covers two coherent domains: workspace file operations and local Git workflow. Each tool has a clear purpose, so the count feels slightly large rather than bloated.

    Completeness3/5

    The file operations cover common file and directory workflows but lack directory copy/move and file metadata/search. The Git side covers status/diff/log/add/commit but omits branch creation/checkout/deletion and unstage, leaving notable gaps in common local Git workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues