Skip to main content
Glama
Sign In
research-bridge

research-bridge

by MrWolffy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to research-bridge

No user-submitted related servers found.

    Related Servers

    • Project OS for Codex MCP

      dang748
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Codex projects to read Git-backed kickoff, acceptance, handoff, progress, and next-step context, and to append validated, audited progress events through scoped MCP tools. This supports visible agent progress, resumable sessions, and safer handoffs.
      MIT

    • ReadOnly Observer

      liuhuijiayou
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives MCP clients a read-only, evidence-based view of explicitly approved local projects and individual Codex sessions, enabling codebase browsing, session review, and comparison of session records against current source and bounded Git history without modifying sources or controlling sessions.
      MIT

    • git-remote-mcp

      abhinav054
      A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to inspect and modify local git repositories by running commands such as status, log, diff, add, commit, branch, and stash. Push operations are not performed locally; instead diffs are sent to a configurable HTTP API that handles the upload, with all other remote git commands blocked.
      27
      MIT

    • lattice

      moulwyse
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides bounded repository context and edit-grant MCP tools to coding agents such as Codex, indexing local repositories and enabling fingerprint-checked patch application.
      23
      Apache 2.0
    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.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools are clearly distinct with specific purposes (e.g., repo_read vs repo_search, codex_status vs codex_events). However, a few pairs like rva_challenge_result/rva_review_result and research_record_followup_decision/research_record_settlement_decision are close in function and could be misselected without careful reading.

    Naming Consistency4/5

    Tool names consistently use snake_case with domain-specific prefixes (repo_, codex_, research_, rva_, bridge_, workstream_), and most follow a verb_noun pattern (e.g., repo_read, codex_start_task). The consistency is strong, though some longer names like research_record_settlement_decision mix multiple nouns but remain readable.

    Tool Count2/5

    With 27 tools, the surface is heavily populated for a single server. Even for a complex research-bridge system with Codex integration, the count exceeds the typical threshold and may overwhelm agents, increasing the risk of misselection and cognitive load.

    Completeness4/5

    The tool set covers the full workflow: repository inspection, Codex task lifecycle (start, status, events, abort, followup), research cycle status, knowledge publishing, migration handling, RVA reviews, and governance actions. Minor gaps exist (e.g., no direct tool for reading knowledge graph entries, only status), but the core lifecycle appears complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources