Skip to main content
Glama
chatre7yos

chatgpt-local-mcp-bridge

by chatre7yos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chatgpt-local-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • Convorel

      MarioJames
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides local, read-only MCP tools that expose a specified workspace's directory listing, file contents, text search, git status, and git diff to AI clients.
      1
      Apache 2.0

    • C2C Bridge

      leowood2000
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables the ChatGPT web app to securely read selected files, git state, and test output from a local workspace through OAuth-protected read-only MCP tools, so TeleAgent retains full execution control.
      MIT

    • Local Supervisor Bridge

      VITASID57
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT web to safely read and modify only explicitly allowed local project files through OpenAI Secure MCP Tunnel, including git operations, file edits, and running project scripts, while enforcing strict security boundaries.
      18
      MIT

    • Kastor

      mno-d
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets ChatGPT or MCP clients work with files on your machine, with tools for reading, editing, searching, git operations, and safety checks.
      MIT

    • ChatGPT MCP Bridge

      haseebgb92
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT Web, connected through OpenAI Secure MCP Tunnel, to browse and search local folders with optional file editing and terminal command execution, and to control an existing Chrome session for navigation, tab management, clicking, typing, screenshots, and DevTools inspection.
      78 npm
      MIT
    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 6 tools

    Disambiguation4/5

    Each tool has a distinct purpose: workspace info, file listing, file reading, text search, git status, and git diff. The only minor ambiguity is that workspace_list could be mistaken for a file-listing tool, but the description clarifies it.

    Naming Consistency3/5

    Names mix verb-first patterns like list_files and read_file with noun-phrase patterns like git_status and git_diff, plus the unusual workspace_list. All names are readable and consistently snake_case, but the convention is not uniform.

    Tool Count5/5

    Six tools is a well-scoped count for a read-only local workspace bridge. Each tool covers a necessary operation without redundancy or bloat.

    Completeness4/5

    The toolset covers the core read-only workspace needs: discover, list, read, search, and inspect git state. Minor gaps like file metadata or git log are not critical for the stated read-only purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources