cli-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLI_BRIDGE_LEAN | No | If set to '1', exposes a curated ~12-tool surface instead of the full set. | |
| APPLE_FM_SERVE_URL | No | URL for Apple Foundation Model server (optional, enables Apple PCC lane). | |
| OPENROUTER_API_KEY | No | API key for the optional OpenRouter lane (hidden until set). | |
| CLI_BRIDGE_HIDE_HOST | No | If set to '1', the host's own lane is kept out of fan-out operations. | |
| CLI_BRIDGE_MAX_DEPTH | No | Maximum delegate re-entry depth (default: 1). | |
| CLI_BRIDGE_LANES_FILE | No | Path to a custom lanes JSON file to extend or override built-in lanes. | |
| CLI_BRIDGE_DEFAULT_CWD | No | Default working directory for delegates when the host provides no workspace root. | |
| CLI_BRIDGE_TRACE_FOOTER | No | Set to 'off' to disable trace footers in responses. | |
| CLI_BRIDGE_DAILY_CREDIT_CAP | No | Hard daily credit cap enforced at spawn. | |
| CLI_BRIDGE_VERIFY_PLAN_READONLY | No | If set to '1', any read-only delegated plan that writes to the git workspace gets flagged. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctorA | Health check: which CLIs are installed, which is the host, paid lanes, defaults, current cost profile. Pass deep=true to also probe each lane with a tiny live call (checks auth/quota — uses a bit of free quota; skips paid lanes). |
| setupA | Show the cost-profile choice (saver/balanced/max) to walk the user through configuring how cli-bridge spends paid credits/quota. Call this on first use if the profile isn't set, ASK the user, then tell them how to set it. |
| usage_reportA | Local usage stats (this machine only): total runs, per-lane counts/success/avg latency, ESTIMATED tokens (chars/4) and credits (if CLI_BRIDGE__CREDITS_PER_1K is set), and recent calls. All token/credit figures are estimates, never exact. |
| usage_budgetA | Per-lane runs since UTC midnight vs an optional CLI_BRIDGE__DAILY_LIMIT (ENFORCED at spawn once reached), plus estimated tokens/credits spent today. Estimates only. |
| lane_statsA | Per-lane health: total runs, failures, consecutive failures/timeouts, and any active cooldown (a lane in cooldown is skipped by ask_all until it clears). |
| reset_lane_stateA | Clear a lane's cooldown + failure counters (e.g. after you re-logged in or your quota reset). Pass the lane key, e.g. 'gemini'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_diff | Multi-model code review of your current git diff. |
| security_review | OWASP-aware multi-model security review of your git diff. |
| debate | Debate a question across several models, then a judge concludes. |
| cost_setup | Configure how cli-bridge spends paid credits/quota (cost profile). |
| premortem | Stress-test a plan across models before building it. |
| test_plan | Derive a prioritized test plan from your git diff across models. |
| apilookup | Look up a library/API in CURRENT docs via a web-aware lane (beats a stale training cutoff). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Effective config | Profile, guard, terse, and per-lane cost/model. |
| Lane health | Per-lane runs/failures/cooldown (JSON). |
| Usage summary | Estimated tokens/credits by lane (JSON). |
| review_diff schema | JSON schema of the structured review result. |
TDQS
Scored across 6 tools
Tools are mostly distinct: doctor focuses on overall health and auth, lane_stats on per-lane health and cooldowns, usage_report on local totals, usage_budget on daily limits, and reset_lane_state on clearing state. Some overlap exists between doctor and lane_stats, but descriptions clarify the boundaries.
Names mix single verbs (doctor, setup) with noun phrases (lane_stats, usage_report, usage_budget, reset_lane_state). The verb_noun pattern is not consistent across the set, though the names themselves are descriptive and readable.
Six tools is well-scoped for a CLI bridge management server, covering health, usage, budget, and state reset without redundancy or bloat.
The domain of monitoring and managing CLI lanes is reasonably covered: health checks, usage stats, daily budgets, and state reset are all present. A minor gap is the lack of a direct configuration tool (e.g., setting the cost profile), though setup guides the user through it.