deepseek-mcp-server

A complete, unrestricted Model Context Protocol server for the DeepSeek API. It exposes DeepSeek's whole surface — chat, reasoning, fill-in-the-middle, prefix completion, function calling, JSON mode, logprobs, streaming — to any MCP client: VS Code, Claude Code, Claude Desktop, Cursor, Windsurf, or your own.

• 12 tools, 7 prompt templates, 5 resources

• No client-side caps. No token ceiling, no output truncation, no path allowlist by default. Every limit is an opt-in environment variable.

• A raw passthrough tool, so endpoints and parameters added to the DeepSeek API after this server was written are reachable without a code change.

• One direct dependency (@modelcontextprotocol/sdk — which brings its own transitive tree, about 95 packages in total) and no build step.

• MIT licensed.

Install

git clone https://github.com/sengarcia32-ux/deepseek-mcp-server.git
cd deepseek-mcp-server
npm install

Register it with every MCP client on the machine:

node install/register.mjs --apply

On Windows you can run the whole thing in one step:

powershell -ExecutionPolicy Bypass -File install\install.ps1

Then add your API key — grab one at https://platform.deepseek.com/api_keys:

powershell -ExecutionPolicy Bypass -File install\set-key.ps1

or edit ~/.deepseek-mcp/config.json by hand:

{ "apiKey": "sk-your-key-here" }

Verify everything end to end:

node bin/deepseek-mcp.js --doctor

Restart VS Code and any Claude client so they pick up the new server.

What register.mjs touches

It merges into existing config and backs up every file it writes (*.bak-<timestamp>).

Clients that aren't installed are skipped. Remove it all again with node install/register.mjs --apply --remove.

No API key is written into any client config. Every client points at the same single source of truth, ~/.deepseek-mcp/config.json, so the key lives in exactly one file.

Related MCP server: DeepSeek MCP Server

Tools

Multi-turn sessions

Pass the same session_id to any chat tool and prior turns are prepended automatically:

{ "prompt": "What is a monad?", "session_id": "fp-lesson" }
{ "prompt": "Now show me one in TypeScript.", "session_id": "fp-lesson" }

Sessions persist to ~/.deepseek-mcp/sessions/. Reasoning traces are deliberately not fed back on later turns, which is what the DeepSeek API requires.

The extra escape hatch

Every chat tool accepts an extra object that is merged into the request body last, so it overrides anything the server set:

{ "prompt": "hi", "extra": { "seed": 42, "some_new_param": true } }

Prompts

deepseek-code-review, deepseek-debug, deepseek-explain, deepseek-write-tests, deepseek-optimize, deepseek-reason, deepseek-translate.

In VS Code these appear as / commands in the chat input once the server is running.

Resources

deepseek://config, deepseek://models, deepseek://sessions, deepseek://stats, deepseek://log.

Configuration

First match wins: process environment → <package>/.env → ~/.deepseek-mcp/config.json → built-in default.

config.json also takes extraHeaders and defaultBody objects, applied to every request.

Running against a different provider

baseUrl is not validated, so the server works against anything speaking the OpenAI chat completions shape — DeepSeek, a local Ollama or vLLM instance, OpenRouter, a gateway of your own:

{ "baseUrl": "http://localhost:11434/v1", "apiKey": "ollama", "chatModel": "deepseek-r1:14b" }

CLI

node bin/deepseek-mcp.js              # run the MCP server on stdio (what clients do)
node bin/deepseek-mcp.js --doctor     # print config and test the connection
node bin/deepseek-mcp.js --list-tools
node bin/deepseek-mcp.js --version

Tests

npm test

Launches the real server over stdio with an MCP client and runs 27 protocol-level checks. No API key needed — the key-dependent path is asserted to fail with actionable guidance instead.

A note on "unrestricted"

The defaults here are permissive on purpose: no token caps, no output truncation, and deepseek_analyze_files can read anywhere the Node process can. That means an MCP client driving this server can send the contents of local files to DeepSeek's API. That is the point of the tool, but it is worth knowing.

If you want it narrower, the knobs are all there:

{
  "allowFs": true,
  "fsRoots": ["C:\\Users\\you\\projects"],
  "maxBytesTotal": 1000000
}

Or "allowFs": false to turn local file reads off entirely. Prompts, file contents and responses are not logged at info level; raise to debug or trace only when you need it, and note that trace puts request bodies in the log file.

License

MIT. See LICENSE.

Not affiliated with or endorsed by DeepSeek or Anthropic.