M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionDeepSeek MCP ServerMCP server for DeepSeek V4.1 Flash chat, Responses, FIM, and Files APIsGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS64 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience15 / 2014 / 20
Best for
  • Developers integrating DeepSeek V4.1 Flash into MCP clients
  • Chat or analysis workflows that combine text and image inputs
  • Users who want to self-host the server over stdio or a local streamable-http endpoint
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who need image, video, or audio generation (this server is image understanding only)
  • Users looking for an officially DeepSeek-maintained server
  • Environments without a DeepSeek API key or network access to the DeepSeek API
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires the DEEPSEEK_API_KEY environment variable to make upstream DeepSeek API requests
  • The hosted endpoint at https://deepseek-mcp.ragweld.com/mcp requires Authorization: Bearer <token>
  • upload_file sends base64 image data that is stored by DeepSeek under your account
  • Local streamable-http mode binds a host and port and can enforce an origin allowlist via MCP_HTTP_ALLOWED_ORIGINS
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Data uploaded via upload_file is stored by DeepSeek under your account and persists unless you set an expiry or call delete_file; expiry must be between 3,600 and 2,592,000 seconds
  • Uploads are limited to 64 MiB and signature-checked before upload; upload_file does not accept local file paths and does not fetch arbitrary URLs on the server
  • Conversation memory lives in the process, is cleared on restart, and is bounded by CONVERSATION_MAX_MESSAGES
  • The hosted deployment has its own release cycle and may lag the npm/GitHub release, so inspect tools/list before relying on a new tool
  • This server is community-maintained and is not an official DeepSeek release
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Codex, Claude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1115