shemcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHEMCP_ROOT | No | Override the sandbox root directory. If not set, falls back to git repository root or current working directory. | |
| MCP_SANDBOX_ROOT | No | Alternative environment variable to override the sandbox root. |
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 |
|---|---|
| shell_execA | Execute an allow-listed command within the sandbox (git project root). Optional cwd must be a relative path from the sandbox root, or an absolute path within the sandbox or a valid git worktree. Supports pagination via limit_bytes and next_cursor (page and cursor are required for pagination). Automatically spills large outputs to file with spill_uri. |
| read_file_chunkA | Reads paginated data from a spilled file (stdout or stderr). Accepts cursor and limit_bytes to safely stream contents. |
| shell_infoA | Get sandbox information including the sandbox root path, allow/deny command policy, and server version. |
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 clear, distinct purpose: reading spilled output, executing commands, and retrieving sandbox info. No overlap exists.
All tool names follow a consistent verb_noun pattern with snake_case: read_file_chunk, shell_exec, shell_info.
Three tools is on the low end but appropriate for a focused sandbox execution server. The scope is narrow yet complete enough.
Core operations (execute, read output, info) are covered, but missing features like managing spilled files, listing sandbox contents, or aborting commands represent notable gaps.