Skip to main content
Glama
szkeli

Local Computer Bridge

by szkeli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Local Computer Bridge

No user-submitted related servers found.

    Related Servers

    • open-chatgpt-on-mac

      zhanglili31
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT's web interface to operate a real Mac by executing shell commands and reading or writing files over a reverse SSH tunnel, without installing a client or consuming API quota.
      MIT

    • Keyhole – Local files for

      L-Jovi
      A
      license
      A
      quality
      A
      maintenance
      Read selected local folders from ChatGPT on macOS, with per-folder read-only or read-write access and hash-checked, recoverable edits. Requires local installation and a private ChatGPT app. The Glama container is a synthetic evaluation demo; it does not connect to files on your Mac.
      12
      1
      MIT

    • chatgpt-sol-local-bridge

      Pandorka132
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT to operate a local workstation through a secure outbound tunnel, exposing 44 MCP tools for files, git, projects, processes, browsers, native apps, Office documents, and optional Codex delegation across macOS, Linux, and Windows.
      MIT

    • Workspace Bridge

      Asutorufa
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT to access and manage registered local development projects through controlled file, command, process, and Git operations, with batch tools, permission modes, and tunnel-based remote forwarding.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: read (file contents), write (full overwrite), edit (targeted single replacement), and bash (shell execution). The descriptions explicitly cross-reference each other, e.g. telling the agent to use bash for directory listings and edit for targeted changes, eliminating overlap.

    Naming Consistency4/5

    read, write, and edit are consistent lowercase action verbs, but bash is a noun naming the shell rather than the operation. The deviation is minor and intuitive, so the set remains highly readable.

    Tool Count5/5

    Four tools is well-scoped for a local file/shell bridge, with no redundancy. Each tool (read, write, edit, bash) earns its place by covering a necessary and non-overlapping capability.

    Completeness4/5

    The surface covers reading, creating, overwriting, editing, and arbitrary shell work, so file delete/list/move are reachable through bash. A dedicated delete or list tool is absent, but the bash escape hatch makes this a minor gap rather than a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources