dsh-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DSH_OPS_ROOTS | Yes | Explicitly configure the allowed project directories. Use colon as separator on macOS/Linux, semicolon on Windows. The service only allows reading, writing, searching, copying, and verifying files within these root directories. | |
| DSH_OPS_STATE_DIR | No | Change the storage directory for batch results. Default is the local application state directory. | |
| DSH_OPS_ENABLE_LEGACY_TOOLS | No | Set to 1 to enable legacy tools (ops_inspect_local_file, ops_glob, ops_grep) for backward compatibility during migration. Restart the MCP service after setting. | 0 |
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 |
|---|---|
| ops_batchA | Execute 1-512 related allowlisted file operations in one call. grep_many searches 2-20 literal terms in one filesystem pass; a single-step search preview maps each query to [path, line] pairs, with snippets available through ops_result. Mutating batches require a stable idempotency_key on retries. |
| ops_resultC | Retrieve batch results by page, fields, step_ids, operations, states, literal path_prefix, or grep_many queries; or release the reference. |
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 2 tools
ops_batch executes file operations, while ops_result retrieves or releases batch results. The action and resource are clearly distinct, so an agent should not confuse them.
Both tools use the same ops_ prefix and snake_case object style. There are no mixed conventions or vague labels within the pair.
Two tools is thin for a file-operations server, even though ops_batch is broad and ops_result handles retrieval. It falls below the typical 3-15 tool range and leaves little room for discovery or control operations.
The set covers batch execution, result retrieval, filtering, and reference release. However, there is no way to discover allowlisted operations or cancel a running batch, which are notable gaps for agent workflows.