MCP servers for DeepSeek

MCP servers on mcprush that work with DeepSeek. DeepSeek is a terminal harness, and working with it is a claim each publisher makes on their own listing — this shelf is every listing that makes it, and nothing else.

DeepSeek can start a server on your own machine or reach a remote one over HTTP, so both halves of this shelf are open to it. Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. Narrowing further — by category, by price model, by how a server authenticates — keeps the client filter on, so nothing on the page stops being about DeepSeek.

A server that runs on its publisher’s infrastructure is reached through the mcprush gateway, so one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set. Installing one is a line of the mcprush CLI — npx mcprush@latest add, followed by the server’s id — and a --client flag writes another client’s config instead of the default one. A server that runs on your own machine carries its publisher’s own instructions instead, and the listing says which of the two it is before you install anything.