Data as of

DeepSeek MCP Server for Cursor: Setup & Config

Cursor: DeepSeek MCP Server exposes DeepSeek V4 generation and account utilities to MCP clients.

What you can do with DeepSeek in Cursor

Pick it for explicit DeepSeek V4 controls plus model, balance, and in-memory conversation utilities.

  • Inspect available models and account balance
  • List or reset conversation histories in the active process

Before you start: DeepSeek in Cursor

  • npx
  • A DeepSeek API key for local mode
  • An MCP-compatible client

This is the local stdio launch. A hosted HTTP alternative is documented at https://deepseek-mcp.ragweld.com/mcp and requires its own bearer token; it is not needed for this local configuration.

DeepSeek Cursor configuration

  1. Choose Cursor configuration scope

    For DeepSeek MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add DeepSeek MCP Server to Cursor

    Use the deepseek-mcp-server entry below in mcpServers. Keep DeepSeek MCP Server's documented stdio connection fields and your other Cursor entries.

  3. Check DeepSeek MCP Server in Cursor

    DeepSeek MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "deepseek-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "deepseek-mcp-server"
      ],
      "env": {
        "DEEPSEEK_API_KEY": "<DeepSeek provider API key>"
      }
    }
  }
}

DeepSeek tools available to Cursor

DeepSeek's stored tool list documents 7 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

chat_completion

Find chat_completion under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Generate DeepSeek V4 chat responses from a message or conversation history.

completion

Find completion under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

create_response

Find create_response under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

list_models

Find list_models under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get_user_balance

Find get_user_balance under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Read account balance and availability without changing account state.

reset_conversation

Find reset_conversation under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Clear one conversation history held by the current MCP process.

list_conversations

Find list_conversations under DeepSeek in Cursor's MCP settings; inspect its arguments when the agent requests a call.

List conversation identifiers currently held in process memory.

DeepSeek: full stored tool descriptions

Troubleshooting DeepSeek in Cursor

  • Cursor must find npx deepseek-mcp-server (Node.js/npm) for DeepSeek MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
  • Review DEEPSEEK_API_KEY for DeepSeek MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
  • DeepSeek MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Conversation history is limited to the current process memory
  • Known limitation: Provider credentials or a hosted bearer token are required
  • Known limitation: Responses API tool appears in structured data but not the README tool list
  • General Cursor troubleshooting lives in the /clients/cursor guide.

DeepSeek MCP Server — details. Cursor guide

Frequently asked questions

Cursor's DeepSeek MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's deepseek-mcp-server example uses stdio.

DeepSeek MCP Server's Cursor configuration invokes npx deepseek-mcp-server (Node.js/npm).

Cursor's DeepSeek MCP Server example references DEEPSEEK_API_KEY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

DeepSeek MCP Server's stored list contains 7 tools, including chat_completion, completion, create_response. Compare those names with Cursor's connected tool list; the stored list is not a live check.

Only in-memory histories in the current MCP process are described.

Local mode uses DEEPSEEK_API_KEY. The hosted endpoint uses a bearer token shown as DEEPSEEK_MCP_AUTH_TOKEN in client examples.