DeepSeek MCP Server
The DeepSeek MCP Server provides an interface to DeepSeek's language models, enabling:
Natural Language Interactions: Query models, settings, and configuration options
Model Management: Switch between
deepseek-reasoner(default) anddeepseek-chatmodels manually or via automatic fallbackConfigurable Parameters: Adjust temperature, max tokens, top-p, presence/frequency penalties
Multi-turn Conversations: Maintain context and message history across exchanges
MCP Integration: Work with MCP-compatible applications like Claude Desktop
Testing & Debugging: Use MCP Inspector to test completions and monitor performance
Proxy Functionality: Maintain anonymity by exposing only a proxy to external clients
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DeepSeek MCP Serverstart a conversation with deepseek-chat and set temperature to 0.7 for creative responses"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DeepSeek MCP Server
Model Context Protocol server for the current DeepSeek V4 API.
As of August 18, 2026, DeepSeek's public API reference documents:
POST /chat/completionswithdeepseek-v4-flashanddeepseek-v4-proPOST /responseswith native OpenAI Responses API request and response shapesPOST /beta/completionsfor V4 Pro FIM completionGET /modelsGET /user/balance
This server exposes only those documented API surfaces. It does not ship a V4 monitor, speculative image/video/upload tools, or automatic model substitution.
Tools
chat_completion: DeepSeek V4 chat. Defaults todeepseek-v4-flash. Supportsthinking: { "type": "enabled" | "disabled" },reasoning_effort: "low" | "high" | "max", JSON output, function tools, logprobs, streaming, and conversation memory.create_response: Stateless native Responses API calls with text or structured input, reasoning effort controls, function tools, server-side web search, structured output, and semantic streaming.completion: DeepSeek V4 Pro FIM completion. Defaults todeepseek-v4-pro.list_models: Reads the live DeepSeek model list.get_user_balance: Reads account balance and availability.reset_conversation: Clears an in-memory conversation.list_conversations: Lists in-memory conversation IDs.
Related MCP server: DeepSeek MCP Server
Hosted Remote
URL:
https://deepseek-mcp.ragweld.com/mcpAuth:
Authorization: Bearer <token>
Codex CLI:
export DEEPSEEK_MCP_AUTH_TOKEN="REPLACE_WITH_TOKEN"
codex mcp add deepseek --url https://deepseek-mcp.ragweld.com/mcp --bearer-token-env-var DEEPSEEK_MCP_AUTH_TOKENClaude Code:
export DEEPSEEK_MCP_AUTH_TOKEN="REPLACE_WITH_TOKEN"
claude mcp add --transport http deepseek https://deepseek-mcp.ragweld.com/mcp --header "Authorization: Bearer $DEEPSEEK_MCP_AUTH_TOKEN"Cursor:
node -e 'const fs=require("fs"),p=process.env.HOME+"/.cursor/mcp.json";let j={mcpServers:{}};try{j=JSON.parse(fs.readFileSync(p,"utf8"))}catch{};j.mcpServers={...(j.mcpServers||{}),deepseek:{url:"https://deepseek-mcp.ragweld.com/mcp",headers:{Authorization:"Bearer ${env:DEEPSEEK_MCP_AUTH_TOKEN}"}}};fs.mkdirSync(process.env.HOME+"/.cursor",{recursive:true});fs.writeFileSync(p,JSON.stringify(j,null,2));'Local Stdio
DEEPSEEK_API_KEY="REPLACE_WITH_DEEPSEEK_KEY" npx -y deepseek-mcp-serverDocker:
docker pull docker.io/dmontgomery40/deepseek-mcp-server:0.5.0
docker run --rm -i -e DEEPSEEK_API_KEY="REPLACE_WITH_DEEPSEEK_KEY" docker.io/dmontgomery40/deepseek-mcp-server:0.5.0Environment
Required:
DEEPSEEK_API_KEY=your-api-keyOptional:
DEEPSEEK_BASE_URL=https://api.deepseek.com
DEEPSEEK_REQUEST_TIMEOUT_MS=120000
DEEPSEEK_DEFAULT_MODEL=deepseek-v4-flash
MCP_TRANSPORT=stdio
MCP_HTTP_HOST=127.0.0.1
MCP_HTTP_PORT=3001
MCP_HTTP_PATH=/mcp
MCP_HTTP_STATEFUL_SESSION=false
MCP_HTTP_ALLOWED_ORIGINS=https://app.example.com,http://localhost:3000
CONVERSATION_MAX_MESSAGES=200MCP_HTTP_ALLOWED_ORIGINS is only needed for browser-based clients. Streamable HTTP requests that send an Origin header are rejected with 403 unless the exact origin appears in this comma-separated allowlist; normal MCP clients that omit Origin are unaffected.
Verification
npm run build
npm test
DEEPSEEK_API_KEY="REPLACE_WITH_DEEPSEEK_KEY" npm run test:live
DEEPSEEK_MCP_AUTH_TOKEN="REPLACE_WITH_TOKEN" npm run test:remoteThe live smoke test performs real DeepSeek requests for model listing, balance, non-thinking chat, thinking streaming chat with reasoning_content, a native Responses API call, FIM completion, and MCP tool calls.
Protocol Compatibility
This release uses the supported @modelcontextprotocol/sdk v1 line and the 2025-era MCP initialization flow. Migrating to the split v2 packages and the 2026-07-28 protocol era is intentionally outside this maintenance update because it changes lifecycle and packaging contracts rather than being a drop-in dependency bump.
Registry Identity
MCP Registry name:
io.github.DMontgomery40/deepseeknpm package:
deepseek-mcp-serverOCI package:
docker.io/dmontgomery40/deepseek-mcp-server:0.5.0
Official References
DeepSeek chat completions: https://api-docs.deepseek.com/api/create-chat-completion
DeepSeek Responses API: https://api-docs.deepseek.com/api/create-response
DeepSeek FIM completions: https://api-docs.deepseek.com/api/create-completion
DeepSeek models: https://api-docs.deepseek.com/api/list-models
DeepSeek balance: https://api-docs.deepseek.com/api/get-user-balance
MCP specification: https://modelcontextprotocol.io/specification/2026-07-28
MCP TypeScript SDK v2 migration guide: https://github.com/modelcontextprotocol/typescript-sdk/blob/main/docs/migration/upgrade-to-v2.md
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables seamless integration between Ollama's local LLM models and MCP-compatible applications, supporting model management and chat interactions.131,144171AGPL 3.0
- AlicenseDqualityDmaintenanceAllows seamless integration of DeepSeek's language models with MCP-compatible applications like Claude Desktop, supporting features such as model selection, temperature control, and multi-turn conversations with automatic model fallback.24952MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates local language models (like Qwen3-8B) with MCP clients, providing tools for chat, code analysis, text generation, translation, and content summarization using your own hardware.
- AlicenseAqualityAmaintenanceMCP server for DeepSeek AI models (Chat + Reasoner). Supports multi-turn sessions, model fallback with circuit breaker, function calling, thinking mode, JSON output, multimodal input, and cost tracking.351717MIT
Related MCP Connectors
Connect MCP clients to 2,000+ AI models without managing provider API keys.
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for GLM chat completions using Zhipu AI models via AceDataCloud
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DMontgomery40/deepseek-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server