agent-context-bridge
Related Servers
Alternatives to agent-context-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server and CLI that keep project decisions, their reasons, learnings, and next steps in a local SQLite record. AI agents can retrieve earlier context, record project choices, and resume work across sessions; ordinary local use needs no dashboard account.15577 npmApache 2.0
- AlicenseNot gradedqualityCmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with shared project memory, compact evidence-first context, status checks, durable handoffs, and encrypted cross-device checkpoints through MCP.1AGPL 3.0
- AlicenseAqualityDmaintenanceProvides shared real-time context for Claude Code agents, including scope awareness, prior decisions, and anti-overlap, using only files in the repo.5MIT
- AlicenseBqualityBmaintenanceEnables MCP-compatible coding agents to share persistent project context, task claims, handoffs, decisions, test reports, and searchable history through a local or team-hosted SQLite-backed service with a React dashboard.1029 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables two local coding agents to read each other's user-visible history, search past decisions with source tracing, and save confirmed conclusions into a shared memory. Also supports credential-status checks and limited task handoff between Codex and Antigravity over MCP stdio.MIT
TDQS
Scored across 2 tools
The two tools are clearly distinct: acb_search queries records, while acb_status reports workspace/store health. There is no plausible overlap in selection, and the descriptions reinforce the boundary between search and diagnostics.
Both tools use the same acb_ prefix and a consistent lowercase snake_case noun/verb style. The naming pattern is predictable and easy to extend.
Two tools is thin for a bridge/server that implies shared context lifecycle operations beyond read-only search and diagnostics. The small surface is coherent but leaves the server feeling like a partial read-only facade.
The surface lacks write/append/inject/list/prune operations despite references to an 'inject' workflow and a shared context store. Agents can inspect or search existing context but cannot create or manage records, which is a significant lifecycle gap.