DeepSeek Subagent MCP Server
# DeepSeek Subagent MCP Server
MCP server that lets **Codex** (or any MCP client) delegate sub-tasks to **DeepSeek** as a sub-agent.
Single tool `deepseek_task`: give it a task (+ optional context), get back DeepSeek's final answer.
## Features
- 🧠 Single tool `deepseek_task` — delegate independent work (research/draft/review/refactor/analysis)
- 💰 Defaults to **deepseek-v4-flash** (cost-effective), switch to `deepseek-v4-pro` via env
- 🔍 Surfaces `reasoning_content` (V4 thinking mode) as a `<thinking>` block
- ⚡ Zero non-MCP dependencies, one-line `npx` deploy
## Requirements
- Node.js >= 18
- A DeepSeek API key: https://platform.deepseek.com
## Install & run
```bash
cd deepseek-subagent-mcp-server
npm install
npm start
```
## Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
| `DEEPSEEK_API_KEY` | ✅ | — | Your DeepSeek API key. |
| `DEEPSEEK_MODEL` | | `deepseek-v4-flash` | Model. Also `deepseek-v4-pro`. |
| `DEEPSEEK_BASE_URL` | | `https://api.deepseek.com` | Override endpoint (for proxies). |
| `DEEPSEEK_MAX_TOKENS` | | `8192` | Default max output tokens. |
## Codex config
Add to Codex's MCP configuration:
```json
{
"mcpServers": {
"deepseek-subagent": {
"type": "stdio",
"command": "npx",
"args": ["-y", "deepseek-subagent-mcp-server"],
"env": {
"DEEPSEEK_API_KEY": "your-deepseek-api-key",
"DEEPSEEK_MODEL": "deepseek-v4-flash"
}
}
}
}
```
Or run from a local checkout:
```json
{
"mcpServers": {
"deepseek-subagent": {
"command": "node",
"args": ["D:\\GitHub\\MCP\\deepseek-subagent-mcp-server\\src\\index.js"],
"env": {
"DEEPSEEK_API_KEY": "your-key-here"
}
}
}
}
```
## Tool: `deepseek_task`
| Parameter | Type | Required | Description |
|---|---|---|---|
| `task` | string | ✅ | The sub-task for DeepSeek. Be specific about what to do and output format. |
| `context` | string | | Optional context material (code, notes, snippets). |
| `system` | string | | Optional custom system prompt (defaults to a subagent persona). |
| `max_tokens` | number | | Max output tokens. Default 8192. |
| `temperature` | number | | 0-2. Omit to use model default. |
## Example usage
```
# Delegate a code review
deepseek_task(task="Review this function for bugs and edge cases", context="<code>...")
# Delegate a research task
deepseek_task(task="Summarize the key risks of a subscription pricing model")
```
## Related projects
- [minimax-vision-mcp-server](https://github.com/kira4094/minimax-vision-mcp-server)
- [kimi-vision-mcp-server](https://github.com/kira4094/kimi-vision-mcp-server)
- [doubao-vision-mcp-server](https://github.com/kira4094/doubao-vision-mcp-server)
- [glm-vision-mcp-server](https://github.com/kira4094/glm-vision-mcp-server)
- [qwen-vision-mcp-server](https://github.com/kira4094/qwen-vision-mcp-server)
## License
MIT
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.