Skip to main content
Glama
arizen-dev

deepseek-mcp

by arizen-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEEPSEEK_API_KEYYesRequired. Your DeepSeek API key.
DEEPSEEK_MCP_LOGNoSet to '1' to log call metadata to ~/.deepseek-mcp/calls.jsonl (no prompts logged).
DEEPSEEK_BASE_URLNoAPI base URL (change for proxy/compatible providers).https://api.deepseek.com

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
deepseekA

Fast, cheap task execution via DeepSeek V4 Flash (non-thinking mode). Best for: classification, summarization, JSON edits, table generation, template population, pattern-copy refactors, inbox triage. Not for: architecture decisions, judgment under ambiguity, security policy, client-facing final prose. Typical latency: 2-5s. Use advise when you need deeper reasoning.

adviseA

Deep reasoning via DeepSeek V4 Pro with thinking mode enabled. Use when deepseek is not sufficient: judgment under ambiguity, architectural tradeoffs, second opinions on consequential decisions, complex multi-factor analysis, or anything where being wrong has real cost. Defaults to effort=max — exhaustive reasoning. Returns structured response: CONCLUSION / REASONING / WATCH OUT. More expensive (~6x flash) and slower (60-120s). Use effort=medium or high only when you need a quicker lighter read.

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

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'deepseek' for fast, cheap tasks and 'advise' for deep reasoning. Descriptions explicitly state when to use each, leaving no ambiguity.

Naming Consistency2/5

The tool names follow no consistent pattern: 'deepseek' is a product name, while 'advise' is an imperative verb. They do not share a common structure, which could confuse agents expecting a uniform naming convention.

Tool Count5/5

With only 2 tools, the server is well-scoped for its purpose of providing two complementary reasoning modes. The count is appropriate and not excessive or insufficient.

Completeness5/5

The server covers the full spectrum of reasoning needs: fast execution via 'deepseek' and deep reasoning via 'advise'. There are no obvious gaps in the tool surface for the stated domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources