dsh-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DSH_MODEL | Yes | Model name to use | |
| DSH_BACKEND_TYPE | Yes | Type of backend (e.g., ollama, vllm, lmstudio, freetoken, deepseek) | |
| DSH_MODEL_ENDPOINT | Yes | Endpoint URL for the model backend |
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 |
|---|---|
| dsh_run_taskA | Dispatch an autonomous coding task to DeepSeek Harness in headless mode using the configured local/free model. The worker operates directly on the specified repository, reasons autonomously, creates/edits files, executes bash commands, tracks git diffs, and returns structured execution results with zero front-end token burn. |
| dsh_doctorA | Health-check the DeepSeek Harness setup. Checks DSH binary installation, ~/.dsh/settings.yaml configuration, model endpoint connectivity, and Web UI status. |
| dsh_web_statusB | Check if the DeepSeek Harness Web UI is currently running on port 3080, and list active sessions count. |
| dsh_web_startA | Start the DeepSeek Harness Web UI companion in background daemon mode on port 3080 (http://127.0.0.1:3080). |
| dsh_web_stopA | Stop the running DeepSeek Harness Web UI companion process on port 3080. |
| dsh_list_sessionsA | Discover and list existing DeepSeek Harness sessions stored in ~/.dsh/sessions/, sorted by most recent. |
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 6 tools
Each tool targets a distinct concern: running tasks, checking setup health, checking/starting/stopping the web UI, and listing sessions. There is no meaningful overlap, and descriptions make the boundaries clear.
All tools share the 'dsh_' prefix and mostly follow verb_noun (run_task, list_sessions) or web_verb patterns (web_start, web_stop, web_status). 'dsh_doctor' is the only outlier, being a noun rather than a verb phrase, but it is still readable and intuitive.
Six tools is well-scoped for an agent-management server: one primary action, three for web UI lifecycle, one health check, and one session discovery. No tool feels redundant or missing as a lightweight utility.
The core workflows are covered: run a task, check health, manage the web UI, and list sessions. Minor gaps exist (e.g., no session termination or task cancellation), but these are not obvious dead ends for the server's stated purpose.