mcp-server-deepseek
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-deepseekReason step-by-step: explain the concept of supply and demand"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-deepseek
A Model Context Protocol (MCP) server that provides access to DeepSeek-R1's reasoning capabilities, allowing non-reasoning models to generate better responses with enhanced thinking.
Overview
This server acts as a bridge between LLM applications and DeepSeek's reasoning capabilities. It exposes DeepSeek-R1's reasoning content through an MCP tool, which can be used by any MCP-compatible client.
The server is particularly useful for:
Enhancing responses from models without native reasoning capabilities
Accessing DeepSeek-R1's thinking process for complex problem solving
Adding structured reasoning to Claude or other LLMs that support MCP
Related MCP server: DeepSeek MCP Server
Features
Access to DeepSeek-R1: Connects to DeepSeek's API to leverage their reasoning model
Structured Thinking: Returns reasoning in a structured
<thinking>formatIntegration with MCP: Fully compatible with the Model Context Protocol
Error Handling: Robust error handling with detailed logging
Installation
Prerequisites
Python 3.13 or higher
An API key for DeepSeek
Setup
Clone the repository:
git clone https://github.com/yourusername/mcp-server-deepseek.git cd mcp-server-deepseekCreate a virtual environment:
python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activateInstall the package:
pip install -e .Create a
.envfile with your DeepSeek API credentials:cp .env.example .envEdit the
.envfile with your API key and model details:MCP_SERVER_DEEPSEEK_MODEL_NAME=deepseek-reasoner MCP_SERVER_DEEPSEEK_API_KEY=your_api_key_here MCP_SERVER_DEEPSEEK_API_BASE_URL=https://api.deepseek.com
Usage
Running the Server
You can run the server directly:
mcp-server-deepseekOr use the development mode with the MCP Inspector:
make devMCP Tool
The server exposes a single tool:
think_with_deepseek_r1
This tool sends a prompt to DeepSeek-R1 and returns its reasoning content.
Arguments:
prompt(string): The full user prompt to process
Returns:
String containing DeepSeek-R1's reasoning wrapped in
<thinking>tags
Example Usage
When used with Claude or another LLM that supports MCP, you can trigger the thinking process by calling the tool:
Please use the think_with_deepseek_r1 tool with the following prompt:
"How can I optimize a neural network for time series forecasting?"Development
Testing
For development and testing, use the MCP Inspector:
npx @modelcontextprotocol/inspector uv run mcp-server-deepseekLogging
Logs are stored in ~/.cache/mcp-server-deepseek/server.log
The log level can be configured using the LOG_LEVEL environment variable (defaults to DEBUG).
Troubleshooting
Common Issues
API Key Issues: Ensure your DeepSeek API key is correctly set in the
.envfileTimeout Errors: Complex prompts may cause timeouts. Try simplifying your prompt
Missing Reasoning: Some queries might not generate reasoning content. Try rephrasing
Error Logs
Check the logs for detailed error messages:
cat ~/.cache/mcp-server-deepseek/server.logLicense
MIT
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Acknowledgements
Thanks to the DeepSeek team for their powerful reasoning model
Built with the Model Context Protocol framework
Available Tools
1 toolthink-with-deepseek-r1C
Ask deepseek-R1 for user's prompt
Arg: prompt: user's full prompt (full text) Return: Enhanced thinking
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description does not disclose any behavioral traits such as side effects, authentication needs, rate limits, or what 'Enhanced thinking' entails. Critical information is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is very short but includes some structure (Arg/Return). However, the phrasing is awkward and lacks clarity, making it less effective than a concise, clear statement.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, description should cover more context. It neglects to explain 'Enhanced thinking', any prerequisites, or return format. Incomplete for a 1-param tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has one parameter 'prompt' with no description. Description adds 'user's full prompt (full text)', clarifying that input should be the complete prompt. This adds value beyond the schema but does not fully compensate for 0% schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states tool takes a prompt and returns enhanced thinking, but phrasing 'Ask deepseek-R1 for user's prompt' is ambiguous. It could be misinterpreted as fetching a prompt rather than processing one. Purpose is somewhat clear but not precise.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. No sibling tools mentioned, and no context about appropriate use cases or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v0.1.1- First observed
think-with-deepseek-r1
TDQS
Only one tool exists, so there is no ambiguity about which tool to use for the task.
The single tool name 'think-with-deepseek-r1' uses hyphens rather than the common snake_case or camelCase, but consistency within the set is perfect.
A single tool for a model interaction server feels insufficient; typically such servers offer multiple tools for different operations.
The tool covers one specific thinking enhancement, but lacks complementary operations like chat or raw output, leaving potential gaps.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for building and testing AI agents with multi-model experimentation and insights.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseBqualityFmaintenanceA Node.js/TypeScript implementation of a Model Context Protocol server for the Deepseek R1 language model, optimized for reasoning tasks with a large context window and fully integrated with Claude Desktop.169MIT
- AlicenseBqualityDmaintenanceA server that enhances Claude's reasoning capabilities by integrating DeepSeek R1's advanced reasoning engine to tackle complex reasoning tasks.11MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that combines DeepSeek R1's reasoning capabilities with Claude 3.5 Sonnet's response generation, enabling two-stage AI processing where DeepSeek's structured reasoning enhances Claude's final outputs.23MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides Claude with a dedicated space for structured thinking during complex problem-solving tasks, helping improve its reasoning capabilities.14116MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tizee/mcp-server-deepseek'
If you have feedback or need assistance with the MCP directory API, please join our Discord server