Developer Tools & Repos MCP Servers

6,075 Developer Tools & Repos MCP servers on Mcprush.

6,075 MCP servers

Scanned where there is a package or repository to read — the grade is on each server's page
Developer Tools & Repos

MCP plugin that saves 98% of your context window. Works with Claude Code, Gemini CLI, VS Code Copilot, OpenCode, and Codex CLI. Sandboxed

4.3k/day 11 tools
Free

Developer Tools & Repos MCP servers on mcprush reach the repository, the review queue and the package registry the work already lives in — reading a diff, opening a pull request, resolving a version, running a command in a sandbox that throws itself away afterwards.

What to look at before installing one is what it is allowed to write. A server that reads a repository and one that can push to it are different risks under the same heading, and the tool surface on each listing says which one you are about to install. 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. The filters on the left narrow it further and the sort at the top decides what comes first.

Nearly every server in this catalogue is connected straight to its publisher: the listing gives the publisher’s own address or start command, and mcprush is not in the path, so nothing is routed, metered or billed here. The exception is a server delivered through the mcprush gateway — there 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, and installing it is a line of the mcprush CLI: npx mcprush@latest add, followed by the server’s id. The listing says which of the two it is before you install anything.

Compare
tick one more