CommandBridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMMAND_BRIDGE_HTTP_HOST | No | HTTP bind address. | 127.0.0.1 |
| COMMAND_BRIDGE_HTTP_PORT | No | HTTP port. | 8800 |
| COMMAND_BRIDGE_TRANSPORT | No | Transport mode: stdio or http. | stdio |
| COMMAND_BRIDGE_BEARER_TOKEN | No | Required in HTTP mode; minimum 32 characters. | |
| COMMAND_BRIDGE_ALLOWED_HOSTS | No | Comma-separated Host header values; required for non-loopback binds. | |
| COMMAND_BRIDGE_ALLOWED_ROOTS | No | Working-directory roots separated by OS path delimiter (default startup directory). | |
| COMMAND_BRIDGE_ALLOWED_SHELLS | No | Comma-separated shell names (default OS-specific). | |
| COMMAND_BRIDGE_EXECUTION_MODE | No | allowlist or unrestricted. | allowlist |
| COMMAND_BRIDGE_MAX_TIMEOUT_MS | No | Maximum requested timeout in milliseconds. | 60000 |
| COMMAND_BRIDGE_PASSTHROUGH_ENV | No | Additional environment variable names inherited by child commands. | |
| COMMAND_BRIDGE_ALLOWED_COMMANDS | No | Comma-separated command names used in allowlist mode (default OS-specific). | |
| COMMAND_BRIDGE_MAX_OUTPUT_CHARS | No | Combined stdout and stderr limit. | 50000 |
| COMMAND_BRIDGE_DEFAULT_TIMEOUT_MS | No | Default command timeout in milliseconds. | 15000 |
| COMMAND_BRIDGE_MAX_PARALLEL_COMMANDS | No | Per-process concurrency limit. | 2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| command_bridge_get_system_infoA | Return operating-system information and the effective CommandBridge command policy. |
| command_bridge_run_commandA | Run one command on this Linux or Windows host. Allowlist mode blocks shell control syntax and unconfigured commands. This tool may change host state when unrestricted mode is enabled. |
| command_bridge_list_audit_eventsA | Return recent CommandBridge command audit events. Commands are redacted; command output, bearer tokens, and environment values are never included. |
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 3 tools
Each tool has a clearly distinct purpose: system info, command execution, and audit events. No overlap in functionality.
All tools share the command_bridge_ prefix followed by a consistent verb_noun pattern (get_system_info, run_command, list_audit_events).
Three tools is a reasonable minimal set for a command execution server focused on running commands, inspecting policy, and auditing. Slightly minimal but well-scoped.
The core lifecycle is covered: inspect policy (system info), execute command, and review audit trail. Missing direct policy modification or async command control, but these are typically outside the scope of a simple command bridge.