Data as of

DeepSeek MCP Server for Windsurf: Setup & Config

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

What you can do with DeepSeek in Windsurf

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

  • Perform fill-in-the-middle text completion with V4 Pro
  • List or reset conversation histories in the active process

Before you start: DeepSeek in Windsurf

  • 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 Windsurf configuration

  1. Choose Windsurf configuration scope

    For DeepSeek MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

  2. Add DeepSeek MCP Server to Windsurf

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

  3. Check DeepSeek MCP Server in Windsurf

    DeepSeek MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.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 Windsurf

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

chat_completion

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for chat_completion.

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

completion

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for completion.

Generate V4 Pro fill-in-the-middle text from a prompt and suffix.

create_response

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for create_response.

list_models

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for list_models.

Retrieve available DeepSeek model identifiers.

get_user_balance

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for get_user_balance.

reset_conversation

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for reset_conversation.

list_conversations

After refreshing DeepSeek in Windsurf settings, check Cascade's tool list for list_conversations.

List conversation identifiers currently held in process memory.

DeepSeek: full stored tool descriptions

Troubleshooting DeepSeek in Windsurf

  • Check npx deepseek-mcp-server (Node.js/npm) on the machine running Windsurf's MCP integration for DeepSeek MCP Server; refresh MCP and inspect Cascade's tools.
  • Check DEEPSEEK_API_KEY for DeepSeek MCP Server; do not bypass a Windsurf permission error with a broad administrator token.
  • DeepSeek MCP Server uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

DeepSeek MCP Server — details. Windsurf guide

Frequently asked questions

Windsurf reads DeepSeek MCP Server under mcpServers in ~/.codeium/windsurf/mcp_config.json on macOS/Linux; Windows uses %USERPROFILE%\.codeium\windsurf\mcp_config.json.

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

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

Windsurf'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 Windsurf's connected tool list; the stored list is not a live check.

No. The README explicitly says automatic model substitution is not included.

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