Skip to main content
Glama
netbka

Local Commander

by netbka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Local Commander

No user-submitted related servers found.

    Related Servers

    • local-mcp

      shworks-25
      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.
      4
      Apache 2.0

    • AKIMCP

      hoang64
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed, OAuth-gated suite of 38 tools that let web AI assistants like Claude, ChatGPT, and Grok work directly on your local machine — reading and editing files, running whitelisted shell commands, searching, querying SQLite, driving browsers and DevTools, managing background tasks and localhost services, and controlling Git, clipboard, notifications, and Postman. This lets users build, debug, and maintain projects, inspect databases and local APIs, and check on long-running jobs from a browser or phone without granting unrestricted shell access.
      -

    • hands

      abhinavshyju
      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

    • ForgeBridge

      t1ktakdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.
      31 npm
      1
      Apache 2.0

    • vibedev-bridge

      hoan9an
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables web-based AI agents such as claude.ai, ChatGPT and Grok to read and edit files and run allowlisted shell commands on your own machine, plus control Chromium, DevTools, ports, git, SQLite and background tasks. Access is exposed over HTTPS with OAuth 2.1 through a swappable public edge (Tailscale Funnel or a Cloudflare tunnel), with a loopback-only control panel for configuration.
      MIT

    • AKIMCP

      andrea35216
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes an OAuth-gated suite of 38 tools that lets web-based AI clients read and edit files, run whitelisted shell commands, search content, use Git and SQLite, drive browsers and DevTools, and reach localhost or LAN services, clipboard, notifications, ports, Postman, and long-running background tasks on your own machine. Everything runs locally with security controls such as folder scoping, command whitelisting, rate limits, and a call log.
      -
    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

    A3.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions clearly separate close pairs like command_run vs parallel_command_run and fs_write vs fs_replace. Minor overlap exists between process_list/scheduler_status (both report running work) and process_start vs command_run (long-running vs bounded), but descriptions disambiguate these well.

    Naming Consistency4/5

    Names use predictable snake_case with namespace prefixes (fs_, git_, process_, agent_) and clear verb+noun ordering like fs_read, git_status, process_kill. A few deviations exist (noun-only project_snapshot, agent_presence/message/monitor lack verbs), but the overall pattern is readable and stable.

    Tool Count4/5

    At 20 tools the server sits at the heavy end, but each tool maps to a recognizable capability across filesystem, git, process control, HTTP, and agent coordination. No obvious filler or redundant duplicates, so the count is justified even if slightly sprawling.

    Completeness4/5

    The surface covers the core local-dev lifecycle: filesystem read/list/search/write/replace, git status/diff/log, command and process execution, and agent messaging/presence. Gaps like fs_delete or git write operations (add/commit/checkout) exist, but these are workable through command_run.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources