Skip to main content
Glama
ygboy1986

DeepSeek-Claude MCP Server

by ygboy1986
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
reasonB
Process a query using DeepSeek's R1 reasoning engine and prepare it for integration with Claude.

DeepSeek R1 leverages advanced reasoning capabilities that naturally evolved from large-scale 
reinforcement learning, enabling sophisticated reasoning behaviors. The output is enclosed 
within `<ant_thinking>` tags to align with Claude's thought processing framework.

Args:
    query (dict): Contains the following keys:
        - context (str): Optional background information for the query.
        - question (str): The specific question to be analyzed.

Returns:
    str: The reasoning output from DeepSeek, formatted with `<ant_thinking>` tags for seamless use with Claude.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'reason' has a clearly defined and distinct purpose.

Naming Consistency5/5

A single tool cannot demonstrate inconsistency in naming patterns. The tool name 'reason' is clear and descriptive for its function.

Tool Count2/5

One tool is typically too few for a server's purpose unless it's extremely narrow. While the tool is well-described, a single tool feels thin and limits the server's utility for broader reasoning tasks.

Completeness2/5

The server's purpose appears to be reasoning integration, but with only one tool, there are significant gaps. There's no ability to manage sessions, handle different reasoning modes, or provide feedback, making the surface incomplete for practical use.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources