bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_API_KEY | Yes | Your Bridge API key (starts with xrkey_v1...), used to authenticate with the Bridge API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_contextC | Read or update Bridge status, branch binding, claims, and scratchpad. |
| bridge_context_pullC | Pull 7-day org context: tasks, quotes, citations, decisions, leases, seams, briefs & 72h corrections. |
| bridge_brief_latestC | Fetch latest ORG/TEAM Morning Briefs and 72h Corrections. |
| bridge_seamC | Log, edit, retract, or list seams (win, decision, friction, handoff). |
| bridge_decideC | List, propose, score, resolve, or check 1-Click Decisions (--to recipients, blocking/advisory). |
| bridge_scopeC | Claim, release, or list cross-worktree file scope leases. |
| bridge_jobC | List, dispatch, claim, complete, or compile capsules for Bridge agent jobs. |
| bridge_factC | Ingest a bounded (<=280 char) verification fact for task reconciliation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| bridge-session-brief | Hydrate an agent at session boot with Bridge repo context, branch state, claims, and open decisions. |
| bridge-escalate-decision | Structured trade-off template for proposing a 1-Click Decision Card in Bridge. |
| bridge-turn-handoff | Structured turn-closure handoff template for releasing scope claims and updating the Bridge scratchpad. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Bridge Workspace Context | Unified snapshot of repo binding, active branch task/job, scope leases, open decisions, and scratchpad notes. |
| Open 1-Click Decisions | Open decision cards with weighted criteria and option rankings. |
| Active Tasks & Queued Jobs | Active workspace tasks and queued agent execution capsules. |
TDQS
Scored across 8 tools
Most tools target recognizable Bridge resources, but bridge_context_pull overlaps significantly with bridge_brief_latest, bridge_seam, bridge_decide, and bridge_scope because it pulls the same data those tools list. bridge_context is also a broad read/update tool that partially overlaps with claims and scratchpad concerns handled elsewhere.
All tools use a consistent bridge_ prefix and snake_case naming. The main deviation is bridge_context_pull, which adds a verb-like suffix while other names are primarily resource nouns.
Eight tools is a well-scoped count for a Bridge collaboration/context server. Each tool maps to a distinct area, and the surface avoids being either too thin or unwieldy.
The server covers core lifecycle operations for seams, decisions, scopes, jobs, briefs, and facts, plus aggregate context pull. Minor gaps remain around task lifecycle operations and richer brief/history retrieval, but most workflows appear supported.