DeepSeek MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPSEEK_API_KEY | Yes | Your DeepSeek API key |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chat_completionA | Primary DeepSeek V4.1 chat tool for text, images, and multi-turn generation. Defaults to |
| completionA | DeepSeek FIM completion tool for prompt/suffix fill-in-the-middle workflows. Defaults to |
| create_responseA | Create a stateless DeepSeek V4.1 response using the OpenAI-compatible Responses API. Defaults to |
| list_modelsA | List available DeepSeek models for model selection and validation. This tool takes no parameters. Use it before passing an explicit model ID to generation tools. |
| get_user_balanceA | Return the current DeepSeek account balance and availability status. This tool takes no parameters and is read-only. Use it for account health checks when diagnosing provider-side failures. |
| upload_fileA | Upload a JPEG, PNG, GIF, or WebP image to DeepSeek and return a reusable |
| list_filesA | List images uploaded to the DeepSeek Files API. Supports cursor pagination, creation-time order, and the |
| retrieve_fileB | Retrieve metadata for one DeepSeek Files API image by |
| delete_fileB | Delete one uploaded DeepSeek image by |
| reset_conversationA | Delete stored in-memory chat history for a |
| list_conversationsA | List all conversation IDs currently stored in this MCP process memory. This tool takes no parameters and does not call the DeepSeek API. Useful for debugging conversation persistence behavior. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| deepseek_chat_starter | Create a reusable starter prompt for DeepSeek chat_completion |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| deepseek-api-endpoints | DeepSeek endpoint/tool mapping exposed by this MCP server |
| deepseek-runtime | Runtime metadata for this MCP process |
| deepseek-models-live | Live model list from DeepSeek /models endpoint |
TDQS
Scored across 11 tools
The three generation tools (chat_completion, completion, create_response) have overlapping capabilities like text/image input and multi-turn support, which could cause confusion. However, their descriptions clearly differentiate use cases (chat vs FIM vs stateless Responses API), and all other tools target distinct resources or actions.
Nine of eleven tools follow a consistent verb_noun pattern (e.g., list_models, upload_file, delete_file). The two exceptions (chat_completion and completion) are noun-only names, but they are conventional and readable, making the set mostly predictable.
The server provides 11 tools, which is well within the ideal 3–15 range. Each tool covers a distinct aspect of the DeepSeek API (generation, file management, account info, conversation memory), with no obvious redundancy or bloat.
The surface covers core generation, file CRUD (upload/list/retrieve/delete), model listing, balance check, and conversation memory management. Minor gaps include no explicit update or detailed inspection of conversations, but these are not critical for typical workflows.