Skip to main content
Glama
liuchongchong1995

DeepSeek MCP Server

by liuchongchong1995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to DeepSeek MCP Server

No user-submitted related servers found.

    Related Servers

    • DeepSeek MCP Server

      DMontgomery40
      A
      license
      A
      quality
      A
      maintenance
      Enables integration of DeepSeek's language models with MCP-compatible applications, offering features like chat completion, custom model selection, and parameter control for enhancing language-based interactions.
      11
      633 npm
      352
      MIT

    • Deepseek MCP Server

      arikusi
      A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      3
      698 npm
      18
      MIT

    • deepseek-mcp

      Korck-lab
      A
      license
      A
      quality
      B
      maintenance
      Bridges 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.
      4
      31 npm
      MIT

    • deepseek-mcp

      arizen-dev
      A
      license
      A
      quality
      D
      maintenance
      Enables using DeepSeek models as a small, cheap supervised worker from any MCP-compatible client, providing fast flash and deep reasoning tools for bounded tasks.
      2
      53
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools have overlapping purposes with unclear boundaries. 'chat_completion' and 'multi_turn_chat' both appear to handle chat interactions, making it difficult for an agent to distinguish when to use each. Without descriptions, the ambiguity is significant, though the small tool count limits confusion.

    Naming Consistency4/5

    The tool names follow a consistent snake_case pattern with clear, descriptive terms. Both 'chat_completion' and 'multi_turn_chat' use similar naming conventions, making them readable and predictable, though the lack of descriptions reduces clarity.

    Tool Count2/5

    With only 2 tools, the server feels thin and under-scoped for a general-purpose 'DeepSeek MCP Server'. This minimal set suggests incomplete coverage of potential functionalities, such as model management or configuration, making it borderline inadequate.

    Completeness2/5

    Inferring the domain as AI chat interactions, the surface is severely incomplete. It lacks essential operations like model selection, parameter tuning, or context management. The two tools provide basic chat functions but leave significant gaps that could cause agent failures in complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources