just-bash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JUST_BASH_PROJECT_ROOT | No | Project dir to mount in the overlay | cwd |
| JUST_BASH_NETWORK_ALLOW | No | Comma-separated URL prefixes (e.g. https://api.github.com/,https://registry.npmjs.org/) | |
| JUST_BASH_MAX_DURATION_MS | No | Max script duration | 30000 |
| JUST_BASH_MAX_OUTPUT_BYTES | No | Max stdout bytes | 1048576 |
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 |
|---|---|
| bash_execA | Execute a bash script in a sandboxed virtual filesystem mounted at the project root. Writes go to an in-memory overlay and do NOT touch the real filesystem unless committed. Network is disabled unless JUST_BASH_NETWORK_ALLOW is set. Supports: cat/cp/ls/find/grep/awk/sed/sort/uniq/jq/sqlite3/xan/yq/tar/tee, optional python3 (CPython WASM) and js-exec (QuickJS) runtimes. |
| sandbox_statusA | Show the current sandbox state: project root, age, exec count, last script, network policy. |
| sandbox_resetA | Discard the current sandbox (drops all in-memory writes) and create a fresh one. Use this when you want to start over from the real project state. |
| realpathA | Resolve a sandbox path to its real filesystem path (for reading or committing). |
| path_existsA | Check if a path exists in the sandbox (overlay + real fs). |
| faf_migrateA | Run |
| faf_syncA | Run |
| faf_scoreA | Run |
| faf_moltbot_syncA | Run |
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 9 tools
Most tools have clearly distinct purposes: bash_exec for sandboxed execution, sandbox_status/reset for sandbox lifecycle, realpath/path_exists for path resolution, and faf_* tools for different faf operations. The faf tools are differentiated by their descriptions (migrate vs sync vs score vs moltbot_sync), though the similar faf_* prefix could cause slight initial confusion.
Naming patterns are mixed: bash_exec and sandbox_reset are verb_noun, sandbox_status is noun_noun, path_exists is noun_verb, realpath is a single word, and faf_* uses a prefix plus verb. There is no uniform convention across the set, though within the sandbox and faf groups the naming is consistent.
Nine tools is well within the ideal 3-15 range and matches the server's dual-purpose scope (sandboxed bash execution and faf project management). Each tool addresses a distinct need without excessive redundancy.
The sandbox functionality is incomplete: bash_exec mentions writes go to an in-memory overlay and 'do NOT touch the real filesystem unless committed', but there is no commit tool to persist those writes. This is a critical missing operation that creates a dead end for agents trying to make changes. The faf toolset covers migrate/sync/score/moltbot_sync but lacks an init or similar setup command.