Skip to main content
Glama
agent-context-bridge

agent-context-bridge

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
--dirYesPath to your project directory containing the .agent_bridge store.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Agent Context Bridge: shared offline memory across coding agents (Hermes, Claude Code, OpenCode, Codex). 2 strictly read-only tools. Call acb_status first to verify the workspace store is initialized and non-empty; then call acb_search to recall past decisions, constraints, and task notes before acting. Recording, pruning, and auditing are CLI-only (acb record/prune/audit) and intentionally unavailable here, so this server can never modify state.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
acb_searchA

Read-only full-text search over the shared agent context store (.agent_bridge/records.jsonl). OR-combined case-insensitive match on topic/summary/details/tags, newest-first. Never writes or prunes; use to find prior decisions before acting. Returns {version, command, query, count, results[], skipped}.

acb_statusA

Read-only workspace diagnostic for the shared context store. Returns {initialized, records, store_bytes, last_updated, targets, version}. Never creates the store; uninitialized workspace returns initialized:false. Use to verify ACB wiring/health before search/inject.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues