deepseek_r1
Generate text using DeepSeek R1 model
Send a prompt to DeepSeek R1 with your own temperature and token ceiling, and get the generated text back in the session.
LABSCO SUMMARY
The tool takes a prompt rather than a message array, so it suits a self-contained question — a proof, a translation, a rewrite — more than a continuing conversation. temperature and max_tokens are the two levers, and they are per call, which makes it practical to ask the same question twice under different settings and compare.
A single-tool bridge to the DeepSeek R1 model. deepseek_r1 takes a prompt, a temperature and a max_tokens, and returns generated text.
A DeepSeek account with an API key in DEEPSEEK_API_KEY, and Node on your PATH.
Build from source — git clone https://github.com/66julienmartin/MCP-server-Deepseek_R1.git
USE CASES
A prompt goes across and generated text comes back, which suits a proof, a translation or a rewrite where the whole question fits in one message.
temperature and max_tokens are per-call, so the same prompt can be run twice under different settings and the two answers put side by side.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
deepseek_r1Generate text using DeepSeek R1 model
BEFORE YOU INSTALL
1 tool when we connected.
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
You clone and build this one yourself.
# Clone and install
git clone https://github.com/66julienmartin/MCP-server-Deepseek_R1.git
cd deepseek-r1-mcp
npm install
# Set up environment
cp .env.example .env # Then add your API key
# Build and run
npm run buildThe clone above creates a directory named MCP-server-Deepseek_R1, and the next line enters deepseek-r1-mcp. Change into MCP-server-Deepseek_R1 instead, or the build steps run in the wrong place.
{
"mcpServers": {
"deepseek_r1": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DEEPSEEK_R1_MCP>/build/index.js"
],
"env": {
"DEEPSEEK_API_KEY": "<YOUR_DEEPSEEK_API_KEY>"
}
}
}
}