Codex DeepSeek Delegate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Optional OpenAI API key for command review when DEEPSEEK_DELEGATE_COMMAND_REVIEWER is set to 'openai' | |
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key for model access | |
| DEEPSEEK_DELEGATE_MOCK | No | Optional; set to '1' to enable mock runner for development | |
| OPENAI_COMMAND_REVIEW_MODEL | No | Optional; model name for GPT command review, e.g., 'gpt-5.5' | |
| DEEPSEEK_DELEGATE_WORKSPACE_ROOT | No | Optional; root directory for workspace, defaults to server startup directory | |
| DEEPSEEK_DELEGATE_COMMAND_REVIEWER | No | Optional; set to 'openai' to enable GPT-based command review for gray-area commands |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegate_taskA | Launches or resumes a DeepSeek child session for a complex task. Use repo-scout for read-only exploration, implementer for code changes, and pass taskId only when continuing the same child task. |
| delegate_executeB | Compatibility wrapper around delegate_task with subagentType=implementer. Prefer delegate_task for new integrations. |
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 overlap significantly: delegate_execute is a specific wrapper for delegate_task with a fixed subagentType. An agent could be confused about which to use, especially since delegate_task can achieve the same result.
Both tools follow a consistent 'delegate_' prefix with underscores, which is a clear and predictable naming pattern.
With only 2 tools, the server's scope feels thin. While it might be sufficient for a narrow purpose, it barely meets the threshold for a functional set.
The server lacks tools for checking task status, listing active tasks, or canceling tasks, which are obvious gaps for a delegation system. The surface is severely incomplete.