deepseek-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | API key for DeepSeek. Required for tool calls; the server will start without it but tool calls will fail. | |
| DEEPSEEK_BASE_URL | No | Base URL for the DeepSeek API. Can point to a Cloudflare AI Gateway endpoint. | https://api.deepseek.com |
| DEEPSEEK_REPO_ROOT | No | Override the repository root that the server operates on. Defaults to the working directory. |
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 |
|---|---|
| review_changesA | Get an independent code review from DeepSeek on the current git changes. The server runs the diff itself, so do NOT paste code into this call — just say which changes to look at. Worth using for substantial changes (a feature, a refactor, anything before a PR); not worth the round trip for one-line edits. Returns findings grouped by severity with file:line anchors. |
| review_filesA | Get a DeepSeek review of complete files rather than a diff. Use when the question is about existing code rather than a change — architecture, a suspected bug, or an unfamiliar module. Pass paths only; the server reads them. |
| consultA | Ask DeepSeek a specific engineering question as a second opinion — design trade-offs, a decision you are unsure about, or a bug you cannot place. Attach files by path rather than pasting them. For multi-turn exchanges, pass the prior turns in |
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 3 tools
Each tool has a clearly distinct purpose: review_changes focuses on git diffs, review_files on complete files, and consult on general engineering questions. There is no overlap or ambiguity in what each tool does.
Two tools follow a consistent verb_noun pattern (review_changes, review_files), while consult is a single verb but still clear and in line with the action-oriented naming. Minor deviation from the review_ prefix but not chaotic.
Three tools is a well-scoped set for the server's purpose of providing DeepSeek-powered code assistance. Each tool covers a distinct need without unnecessary redundancy.
The tool surface covers the full range of use cases for the domain: reviewing changes, reviewing existing files, and asking general engineering questions. No obvious gaps exist for an AI consultation server.