Local Computer Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_BRIDGE_SHELL | No | Bash executable path. | /bin/bash |
| LOCAL_BRIDGE_BASE_DIR | No | Default working directory for relative paths and Bash commands. | $HOME |
| LOCAL_BRIDGE_READ_MAX_LINES | No | Maximum number of lines returned in a single read call. | 5000 |
| LOCAL_BRIDGE_BASH_TIMEOUT_MS | No | Bash command timeout in milliseconds. | 60000 |
| LOCAL_BRIDGE_READ_DEFAULT_LINES | No | Default number of lines returned by the read tool. | 1000 |
| LOCAL_BRIDGE_BASH_MAX_OUTPUT_BYTES | No | Maximum number of bytes retained for each of stdout and stderr. | 102400 |
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 |
|---|---|
| readA | Read a local text file. Use this for file contents; use bash for directory listings, file discovery, grep/ripgrep, git commands, and other shell operations. Paths may be absolute, start with ~/, or be relative to the configured base directory. |
| writeA | Create or completely overwrite a local UTF-8 text file. Parent directories are created automatically. Use edit for a targeted change to an existing file. |
| editA | Make one exact targeted replacement in an existing local text file. old_text must occur exactly once; the call fails if it occurs zero times or more than once. |
| bashA | Run a shell command on the local computer using bash. Commands time out after 600 seconds (maximum 10 minutes). Independent calls can run concurrently; avoid concurrent writes to the same files. Use this for directory listing, file discovery, grep/ripgrep, git, package managers, build/test commands, scripts, network tools, and other CLI work. Commands start in the configured base directory; use cd inside the command when needed. |
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 4 tools
Each tool targets a distinct operation: read (file contents), write (full overwrite), edit (targeted single replacement), and bash (shell execution). The descriptions explicitly cross-reference each other, e.g. telling the agent to use bash for directory listings and edit for targeted changes, eliminating overlap.
read, write, and edit are consistent lowercase action verbs, but bash is a noun naming the shell rather than the operation. The deviation is minor and intuitive, so the set remains highly readable.
Four tools is well-scoped for a local file/shell bridge, with no redundancy. Each tool (read, write, edit, bash) earns its place by covering a necessary and non-overlapping capability.
The surface covers reading, creating, overwriting, editing, and arbitrary shell work, so file delete/list/move are reachable through bash. A dedicated delete or list tool is absent, but the bash escape hatch makes this a minor gap rather than a dead end.