Skip to main content
Glama
haseebgb92

ChatGPT MCP Bridge

by haseebgb92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ChatGPT MCP Bridge

No user-submitted related servers found.

    Related Servers

    • agent-mcp-gateway

      temporary111111
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT Web to securely access local files and run commands via MCP, with optional OpenCode agent mode for autonomous tasks.
      -

    • LocalPilot

      a252937166
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables ordinary ChatGPT web Chat to work directly on a local machine over a private MCP tunnel — reading and editing project files, running shell commands and tests, loading local skills, manipulating images, and driving Chrome — without spinning up a separate coding agent or additional model-generation API calls. It also supports multi-step task plans with persisted execution receipts and acceptance checks so results from real runs are returned to the conversation.
      -

    • chatgpt-sol-local-bridge

      Pandorka132
      A
      license
      Not graded
      quality
      B
      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.
      1
      MIT

    • Windows Local MCP

      yeyiwen2006
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT to read and write local files, view the screen, and operate Windows desktop windows, mouse, and keyboard through MCP stdio and OpenAI's Secure MCP Tunnel.
      7
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role: discovering roots, listing directory contents, inspecting one path, reading text, and recursive searching. The only mild overlap is that list_files and file_info both return metadata, but their scope is clearly differentiated by the descriptions.

    Naming Consistency4/5

    Four of five tools follow a clear verb_noun convention (list_roots, list_files, read_file, search_files). file_info is noun-based rather than get_file_info, which is a minor deviation but still understandable.

    Tool Count5/5

    Five tools is well-scoped for a read-only filesystem bridge. Each tool covers a necessary operation—discovery, listing, metadata, reading, and searching—without redundant surface area.

    Completeness4/5

    The read-only filesystem surface is coherent and covers discovery, navigation, metadata, reading, and search. It lacks write/create/delete operations, but the descriptions consistently frame the server as read-only, so this is a minor scope gap rather than an internal inconsistency.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources