deepseek-as-subagent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_MODE | No | Set to 'off' to disable DeepSeek for the session | |
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key (required, can also be set in config.json) | |
| DEEPSEEK_WORKSPACE | No | Override the sandbox root path |
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 |
|---|---|
| pingA | Health check. Confirms the deepseek-mcp server is alive. Use this before delegate_to_deepseek if you're not sure whether DeepSeek is configured. Returns version, mode (auto/off), and whether config is loadable. |
| delegate_to_deepseekA | Delegate a focused task to DeepSeek as a real sub-agent. DeepSeek runs its own agent loop with Read/Write/Edit/Bash/Glob/Grep/NotebookEdit tools inside the configured workspace. Use this for batch / repetitive / mechanical tasks where you want to save main-conversation tokens and let DeepSeek do the heavy lifting end-to-end. Good fits:
Bad fits (do it yourself instead):
Args: task: Clear description of what DeepSeek should accomplish, including success criteria and file paths involved. context: Optional additional context — project conventions, related files DeepSeek should consider, output format requirements. Include this when project-specific knowledge matters. Returns: A summary of what DeepSeek did, including files affected, turns used, tokens consumed, and any issues. Always verify the result by reading a sample of the affected files before declaring success to the user. |
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
The two tools serve completely distinct purposes: one for delegating tasks to DeepSeek and one for health checking. There is no ambiguity or overlap.
Both tools use snake_case, but 'delegate_to_deepseek' is descriptive while 'ping' is a single-word convention. The pattern is mostly consistent, with a minor deviation.
With only 2 tools, the server is minimal but appropriate for its focused role as a sub-agent delegator. The health check is essential, but more tools (e.g., cancellation) could be added.
The server covers its core purpose: delegating tasks and verifying availability. No obvious missing operations for its narrow scope, though a status polling tool could be useful.