A Command-Line Interface for Trigger.dev projects
6,075 MCP servers
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Drive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agent
Next.js development tools MCP server with stdio transport
MCP server for SAPUI5/OpenUI5 development
Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Local-first knowledge graph for token-efficient code review through MCP and CLI
Model Context Protocol (MCP) server for AI-assisted development of CAP applications.
MCP server for iOS and Android Mobile Development, Automation and Testing
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
A Model Context Protocol server implementation for Nx
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP server for Langsmith SDK integration
MCP server for mobile device interaction — iOS (IDB), Android (ADB), and Appium/BrowserStack
BrowserStack's Official MCP Server
gk is GitKraken on the command line. It makes working across multiple repos easier with Workspaces, provides access to pull requests and
The official Svelte MCP server providing docs and autofixing tools for Svelte development
MCP plugin that saves 98% of your context window. Works with Claude Code, Gemini CLI, VS Code Copilot, OpenCode, and Codex CLI. Sandboxed
Token-efficient code exploration via tree-sitter AST parsing. 70+ languages, 86-99% token savings.
Dead code, security, secrets detection and code quality for Python, TypeScript, Go.
MCP server for ESLint
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.