Deepseek MCP Server
Related Servers
Alternatives to Deepseek MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMulti-model MCP server enabling code generation, visual analysis, and complex reasoning via Qwen3 models.MIT
- AlicenseNot gradedqualityDmaintenanceA Node.js + TypeScript MCP server that proxies to DeepSeek's Chat, Image, and TTS APIs for conversation, image generation, and text-to-speech.MIT
- 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.2327 npm2MIT
- AlicenseAqualityCmaintenanceMCP 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.2MIT
- AlicenseAqualityDmaintenanceMCP server that wraps DeepSeek's AI capabilities into standard MCP tools, supporting three authentication modes including free web-based usage without API keys.6327 npm3MIT
- 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.419 npmMIT
TDQS
Scored across 3 tools
deepseek_chat and deepseek_fim both produce model completions, which could be confused, but the descriptions clearly distinguish conversational/multi-turn use from prefix-suffix infilling. deepseek_sessions is clearly separate as a management utility.
All three tools use a consistent deepseek_<noun/verb> snake_case pattern (chat, fim, sessions) with no style mixing.
Three tools is on the thin side, but each covers a distinct capability (chat, FIM, session management) and earns its place for a chat API wrapper. Slight deduction because deepseek_sessions bundles list/delete/clear operations rather than exposing them separately.
Core chat and completion workflows are covered, and sessions can be listed/deleted/cleared, but there's no explicit session creation and no embeddings or model-listing tool, which are typical gaps for an LLM API server. Agents can mostly work around this since sessions appear to auto-create via session_id.