Deepseek MCP Server
Related Servers
Alternatives to Deepseek MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMulti-model MCP server enabling code generation, visual analysis, and complex reasoning via Qwen3 models.MIT
- FlicenseNot gradedqualityDmaintenanceA Node.js + TypeScript MCP server that proxies to DeepSeek's Chat, Image, and TTS APIs for conversation, image generation, and text-to-speech.-
- 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.2800 npm2MIT
- FlicenseAqualityCmaintenanceMCP server that packages DeepSeek agents as callable tools, offering a bare model for quick Q&A and a full agent capable of executing real coding and file-modifying tasks in a workspace.2-
- AlicenseAqualityDmaintenanceMCP server that wraps DeepSeek's AI capabilities into standard MCP tools, supporting three authentication modes including free web-based usage without API keys.6800 npm1MIT
- AlicenseAqualityBmaintenanceBridges MCP clients to the DeepSeek API for chat completions and model discovery, with an optional locked-down bridge that delegates prompts to local CLI harnesses like Claude, Codex, or opencode.422 npmMIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct capability: chat completion, fill-in-the-middle completion, and session management. There is no overlap in purpose or behavior, so an agent can reliably select the right tool.
All tools share the deepseek_ prefix and use lowercase snake_case, which is predictable. However, the suffix varies in part-of-speech (chat is a verb, fim is an acronym, sessions is a noun), so it is not a strict verb_noun pattern.
Three tools is a well-scoped surface for a model access server: one for interactive chat, one for code infilling, and one for session lifecycle management. Each tool earns its place without redundancy or bloat.
The core model capabilities (chat and FIM) plus session lifecycle management cover the main workflows. Minor gaps exist, such as no explicit session creation tool (sessions are implicitly created via chat) and no way to inspect a session's message history directly.