deepseek

DeepSeek provides an MCP server that acts as a remote endpoint for chat clients to access DeepSeek tools, models, and balance controls through the Model Context Protocol. The project supports both a hosted remote endpoint and self-hosted local deployments via npm (npx), Docker, or a direct Node.js run. To use the remote MCP, you configure your client applications to point at the hosted URL and pass an authorization token stored in an environment variable. Clients like Codex, Claude Code, and Cursor can integrate this MCP server by supplying the endpoint URL and the appropriate Authorization header, enabling access to DeepSeek’s capabilities without embedding model logic directly in chat prompts. When running locally, you can self-host the server using the provided npm/pnpm workflow or Docker image, which requires an API key from DeepSeek.

What you’ll be able to do with this MCP server: it exposes a hosted endpoint for chat/completions/models/balance management and supports the DeepSeek tooling ecosystem via MCP. You can add the DeepSeek MCP as a remote MCP server in clients such as Codex CLI, Claude Code, and Cursor, or run the server locally for private networks. The server is designed to be used with a bearer token for authentication when using the remote endpoint, and with an API key when self-hosting locally. The Quick Install guide provides concrete commands to register the MCP server in various clients and to start the local server in stdio or Docker modes.

Prerequisites:

• Node.js (for npm/npx usage) or Docker if you prefer containerized runs
• Access to a DeepSeek API key for local self-hosted mode (DEEPSEEK_API_KEY)
• Optional: environment variable for the hosted token (DEEPSEEK_MCP_AUTH_TOKEN) when configuring clients

Installation (remote/hosted usage via npx):

1. Set your hosted token (for local token reference when needed):

export DEEPSEEK_MCP_AUTH_TOKEN="REPLACE_WITH_TOKEN"

2. Install and run the MCP server locally via npx (no local installation required):

DEEPSEEK_MCP_TOKEN_ENV=DEEPSEEK_MCP_AUTH_TOKEN npx -y deepseek-mcp-server

Installation (self-hosted local via npm/npx):

1. Ensure you have Node.js installed
2. Run the server locally with an API key:

DEEPSEEK_API_KEY="REPLACE_WITH_DEEPSEEK_KEY" npx -y deepseek-mcp-server

Installation (Docker):

1. Pull and run the official DeepSeek MCP server image:

docker pull docker.io/dmontgomery40/deepseek-mcp-server:0.4.0

# Run with your API key exposed to the container
docker run --rm -i -e DEEPSEEK_API_KEY="REPLACE_WITH_DEEPSEEK_KEY" \
  docker.io/dmontgomery40/deepseek-mcp-server:0.4.0

Note: If you are using a hosted endpoint, you can skip the local installation steps and configure your MCP clients to point at the remote URL.

Tips and common considerations:

• Use the hosted endpoint for rapid setup and multi-device access: https://deepseek-mcp.ragweld.com/mcp. Authenticate with a Bearer token as described in the README.
• For self-hosted setups, protect your API key (DEEPSEEK_API_KEY) and/or the host token (DEEPSEEK_MCP_AUTH_TOKEN) using environment variables and secure secrets management.
• When using clients like Cursor, Codex, or Claude Code, reference the MCP endpoint and supply the Authorization header or the bearer token as demonstrated in the Quick Install section.
• If your deployment is behind a private network, Docker or local Node.js runs provide the best control over secret storage and network access.
• The MCP integration supports remote MCP usage as well as local orchestration for code-execution flows. Plan tool usage accordingly to balance latency, token costs, and reliability.
• Registry identity: MCP Registry name is io.github.DMontgomery40/deepseek.