DeepSeek MCP Patch Worker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | Required API key for DeepSeek | |
| DEEPSEEK_BASE_URL | No | OpenAI-compatible API base URL | https://api.deepseek.com |
| DEEPSEEK_STATE_DIR | No | Directory for background task database | OS user state directory |
| DEEPSEEK_JOB_WORKERS | No | Number of background workers | 2 |
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 |
|---|---|
| generate_patchA | Generate a validated candidate unified diff; this tool never edits the repository. Use deepseek-v4-pro for complex work and deepseek-v4-flash for routine changes. file_context should label each supplied file with its repository-relative path. allowed_paths is the exact list of files the returned patch may add, edit, or delete. On a repair round, send current file contents plus exact test/build failures. |
| review_patchC | Review an untrusted candidate patch and return a corrected replacement diff, or an empty patch when no correction is justified. |
| submit_patch_jobC | Submit a long-running streamed patch job and return a local job ID immediately. |
| get_patch_jobB | Return persisted status and aggregate stream progress for a background job. |
| get_patch_resultC | Return a persisted validated result, or the current non-terminal status. |
| cancel_patch_jobC | Request cooperative cancellation of a background streamed job. |
| get_capabilitiesB | Return local worker capabilities without calling DeepSeek. |
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 7 tools
Each tool targets a distinct operation: generating, reviewing, submitting, canceling, and querying patches. The get_patch_job and get_patch_result are clearly differentiated by status vs. result.
All tools follow a consistent verb_noun pattern in snake_case (e.g., cancel_patch_job, get_patch_result). No mixed conventions or vague verbs.
7 tools is well-scoped for a patch generation and management server. Each tool serves a clear purpose without redundancy or excessive granularity.
The set covers the full lifecycle of patch jobs (generate, review, submit, cancel, monitor, retrieve). Minor gaps exist, such as a tool to list all jobs or delete old results, but core workflows are complete.