DeepSeek Subagent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_MODEL | No | Model. Also deepseek-v4-pro. | deepseek-v4-flash |
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key. | |
| DEEPSEEK_BASE_URL | No | Override endpoint (for proxies). | https://api.deepseek.com |
| DEEPSEEK_MAX_TOKENS | No | Default max output tokens. | 8192 |
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 |
|---|---|
| deepseek_taskA | Delegate a sub-task to DeepSeek as a sub-agent and get back its result. Use this for work that can be done independently: research, drafting, code review, refactoring, analysis, writing, or any self-contained task that shouldn't pollute the main conversation. The caller (Codex) supplies a task description and optional context; DeepSeek completes the task in one shot and returns the final answer (with reasoning, if produced). Default model: deepseek-v4-flash. Override via DEEPSEEK_MODEL env (e.g. DeepSeek-V4-Pro-0813). |
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 1 tool
There is only one tool, so there is no possibility of confusion or overlapping purposes. The tool clearly covers the single action of delegating a sub-task to DeepSeek.
With a single tool, there is no pattern to be inconsistent about. The name 'deepseek_task' is descriptive and follows a clear noun-based naming convention.
One tool is on the thin side; while the server's purpose is narrow, a richer integration might include multiple tools (e.g., different task types or configuration options). The count is borderline but not unreasonable for a single-purpose sub-agent server.
The tool fully covers the stated purpose of delegating a self-contained task and returning the result. Minor gaps exist, such as no way to manage task history or configure multiple output modes, but these are not essential to the core workflow.