Skip to main content
Glama
zcrossoverz

repo-bridge

by zcrossoverz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to repo-bridge

No user-submitted related servers found.

    Related Servers

    • 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

      chenchihcu
      A
      license
      Not graded
      quality
      C
      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,713 npm
      MIT

    • 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,713 npm
      MIT

    • ChatGPT GitHub MCP App

      fellipegoncalvesleite
      F
      license
      Not graded
      quality
      B
      maintenance
      This MCP server bridges ChatGPT to GitHub, letting you use natural language to read repositories, modify code, create branches, and open pull requests while enforcing security policies like repository whitelists and branch protection.
      -
    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.6/5.0

    Scored across 27 tools

    Disambiguation4/5

    The tools mostly target distinct operations—workspace management, file operations, command execution, and git actions are clearly separated. However, write_file/edit_file and run_command/run_build/run_tests/run_lint have overlapping capabilities that could cause misselection, though their descriptions and intended use cases mitigate ambiguity.

    Naming Consistency3/5

    Naming follows several conventions: verb-first (read_file, run_build), domain-prefix-first (workspace_open, git_status, bridge_status), and a few irregular names like repo_open_remote and file_info. While each group is internally consistent, the lack of a single predictable pattern makes the full set harder to navigate.

    Tool Count3/5

    27 tools is a substantial number, but the server's scope spans workspace management, file editing, command execution, and git workflows, so most tools serve a distinct purpose. The count is at the high end but not unreasonable given the breadth; still, it exceeds the typical well-scoped range.

    Completeness4/5

    The tool set covers the main workflows: opening and managing workspaces, reading and editing files, running builds/tests/lints, and common git operations (commit, branch, diff, status, log, restore). Minor gaps exist—no explicit push/pull (though repo_open_remote refreshes clones) and no stash or tag operations—but these are workable via run_command or are intentionally restricted.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources