AI Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIDGE_DB | No | Database path; takes precedence over the default path. The parent directory of a custom path must already exist. | |
| BRIDGE_AGENT | No | AI identity, usually `claude` or `codex`; defaults to `unknown` when unset. Human commands always use `human`. | unknown |
| BRIDGE_FAKE_NOW | No | Only for testing. Format `YYYY-MM-DD HH:MM:SS`; controls business time and claim expiration checks. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_overviewA | 查看公告板全貌：各方状态、文件认领情况、给你的未读消息。开始任务前先调用这个。 |
| update_statusA | 更新你自己的工作状态，让对方知道你在做什么。每完成一步都应更新。 |
| send_messageB | 给对方留言：提问、交接、通知、回复。 |
| read_messagesA | 读取给你的未读消息（读后标为已读）。include_read=true 时显示最近的全部消息。 |
| claim_filesA | 修改文件前先认领，防止和对方同时改同一个文件。有冲突时一个都不认领。 |
| release_filesA | 释放你认领的文件。不传 files 则释放你在该项目的全部认领。 |
| list_projectsB | 列出所有用过 Bridge 的项目。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool maps to a distinct action: overview, status update, message send/read, file claim/release, and project listing. The only mild overlap is bridge_overview vs read_messages, since the overview also surfaces unread messages, but the descriptions make the boundary (aggregate dashboard vs message-only read) reasonably clear.
Six of seven names follow a clean verb_noun pattern (update_status, send_message, read_messages, claim_files, release_files, list_projects), all in consistent snake_case. bridge_overview is the sole deviation in that it omits an explicit verb, but it remains readable and predictable.
Seven tools is well-scoped for a two-agent coordination service. Each tool earns its place covering status, messaging, file locking, and discovery, with no redundant or filler tools.
The surface covers the full coordination lifecycle: discovery (list_projects), state awareness (bridge_overview, read_messages), communication (send_message, update_status), and file locking (claim_files, release_files). Minor gap: no explicit way to delete or edit a sent message, but that is a workaroundable edge case.