Skip to main content
Glama
Harzva

ChatGPT2LocalBridge

by Harzva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to ChatGPT2LocalBridge

No user-submitted related servers found.

    Related Servers

    • DevSpace

      CYZice
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that lets ChatGPT securely read, edit, search, and run code in your local projects via an owner-approved connection.
      1,521 npm
      MIT

    • DevSpace

      chenchihcu
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that gives ChatGPT a secure connection to your local machine, enabling it to read, edit, search, and run code in your projects.
      1,521 npm
      MIT

    • MCPishCode

      alkindivv
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that brings a Codex-style coding workflow to ChatGPT, allowing it to read, edit, search, and run code in your local projects.
      MIT

    • DevSpace

      arthurwangwsx-code
      A
      license
      Not graded
      quality
      A
      maintenance
      This self-hosted MCP server connects an MCP client such as ChatGPT to approved local project folders, enabling file reading and editing, code search, shell command execution, and Git worktree workflows without uploading code to a third party. It also supports mounting external stdio or Streamable HTTP MCP servers as dynamic capabilities.
      1,521 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

    B3.2/5.0

    Scored across 38 tools

    Disambiguation5/5

    Each tool targets a distinct operation within its domain (bridge, file, git, process, task, workspace, etc.). Even within similar domains like file operations, tools like copy, delete, list, mkdir, move, patch, stat, and write are clearly differentiated. No two tools appear to have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent `domain.verb_noun` pattern using lowercase and underscores (e.g., `bridge.activity`, `file.copy`, `git.diff`). This pattern is uniform across all 38 tools, making it easy to predict tool names.

    Tool Count2/5

    With 38 tools, the server's tool count is significantly higher than the typical well-scoped range (3-15). While each tool serves a distinct purpose, the sheer number may overwhelm agents and suggests the server could benefit from consolidation or modularization.

    Completeness4/5

    The tool set covers a wide range of local development workflows including file management, code reading, git operations, process management, task tracking, testing, and workspace management. Minor gaps exist, such as lacking a tool for editing file permissions or handling binary files, but these are non-essential and the core lifecycle is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources