Skip to main content
Glama
tizee

mcp-server-deepseek

by tizee

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> format

  • Integration 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

  1. Clone the repository:

    git clone https://github.com/yourusername/mcp-server-deepseek.git
    cd mcp-server-deepseek
  2. Create a virtual environment:

    python -m venv venv
    source venv/bin/activate  # On Windows: venv\Scripts\activate
  3. Install the package:

    pip install -e .
  4. Create a .env file with your DeepSeek API credentials:

    cp .env.example .env
  5. Edit the .env file 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-deepseek

Or use the development mode with the MCP Inspector:

make dev

MCP 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-deepseek

Logging

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 .env file

  • Timeout 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.log

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Acknowledgements

Available Tools

1 tool
think-with-deepseek-r1C

Ask deepseek-R1 for user's prompt

Arg: prompt: user's full prompt (full text) Return: Enhanced thinking

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYes

TDQS

C2.5/5.0
Behavior2/5

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.

Conciseness3/5

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.

Completeness2/5

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.

Parameters3/5

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.

Purpose3/5

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.

Usage Guidelines2/5

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. 1 tool updatev0.1.1
    • First observedthink-with-deepseek-r1

TDQS

C2.8/5.0
Disambiguation5/5

Only one tool exists, so there is no ambiguity about which tool to use for the task.

Naming Consistency4/5

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.

Tool Count2/5

A single tool for a model interaction server feels insufficient; typically such servers offer multiple tools for different operations.

Completeness3/5

The tool covers one specific thinking enhancement, but lacks complementary operations like chat or raw output, leaving potential gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

Related MCP Servers

Latest Blog Posts

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