Skip to main content
Glama
giaminhgist

deepseek-mcp

by giaminhgist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to deepseek-mcp

No user-submitted related servers found.

    Related Servers

    • deepseek-as-subagent

      PsChina
      A
      license
      A
      quality
      B
      maintenance
      Run DeepSeek as a real sub-agent inside Claude Code / Codex CLI — not just a single LLM call. DeepSeek gets its own 7-tool agent loop (Read/Write/Edit/Bash/Glob/Grep/NotebookEdit) inside a sandboxed workspace.
      2
      52
      MIT

    • Codex DSH MCP

      sakurameishi
      A
      license
      A
      quality
      B
      maintenance
      Enables Codex to delegate routine repository exploration, implementation, refactors, tests, and fixes to DeepSeek Harness in isolated Git worktrees, returning compact results and patches for review while keeping the main workspace protected.
      5
      20 npm
      MIT

    • nuncius

      sdirkse
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code, Codex, and Cursor to delegate self-contained coding tasks to one another on the user's own subscriptions, with each task isolated in a git worktree and sandbox, usage tracked, budgets enforced, and results returned for review.
      438 npm
      2
      Apache 2.0
    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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: deepseek_task covers general repository work, deepseek_review is narrowly scoped to code review of diffs/files, and deepseek_usage reports statistics without making API calls. There is no realistic overlap that would cause an agent to pick the wrong tool.

    Naming Consistency5/5

    All tools follow the same deepseek_ prefix followed by a single descriptive noun: deepseek_task, deepseek_review, deepseek_usage. The naming pattern is uniform and predictable.

    Tool Count5/5

    Three tools is a well-scoped surface for a focused DeepSeek worker integration: one general-purpose execution tool, one specialized review tool, and one usage/accounting tool. Each tool earns its place without redundancy or bloat.

    Completeness4/5

    The surface covers the core operations for this domain: delegating task work, performing reviews, and checking usage/budgets. Minor gaps exist such as explicit cancellation, configuration, or history listing, but these are secondary and likely handled outside the MCP interface.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources