Command-Line Interface for Firebase
1,468 MCP servers
All Azure MCP tools to create a seamless connection between AI agents and Azure services.
MCP server for Hostinger API
Manage Appwrite projects, databases, auth, storage, functions, and messaging; search Appwrite docs
Netlify MCP server that lets code agents use the Netlify API and CLI to create and manage sites and deploys.
Model Context Protocol (MCP) Server for interacting with GCP APIs
CloudBase MCP: DB, functions, storage, hosting via @cloudbase/cloudbase-mcp
Server providing Argo CD integration for MCP clients.
Manage UniFi Network devices, clients, firewall, VLANs, VPNs, and more via MCP.
A server implementing the Model Context Protocol for Pulumi.
A Model Context Protocol (MCP) server for Kubernetes and OpenShift
Official Heroku Platform MCP server for interacting with Heroku apps and platform resources.
Policy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.
Google Cloud tool for deploying applications to Cloud Run via MCP.
Deploy static websites from AI agents. Free at mcp.shipstatic.com — no install, no signup.
Community Kubernetes server: inspect and manage pods, deployments and services.
Cls is an MCP server that runs on your own machine, started by your client over stdio.
Inspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates.
Official Octopus Deploy server that lets AI assistants inspect, query, and diagnose problems within an Octopus instance.
Remote shell and detached long-running jobs on your own machines — no SSH, open ports or VPN.
Community Docker server: manage containers, images, volumes and networks in natural language.
Cloud & DevOps MCP servers on mcprush reach the infrastructure side of the work: build pipelines, deploys and rollouts, on-call rotas and the incident record that forms around them.
What to look at before installing one is which of its actions are destructive and what stands in front of them. A listing that gates its writes says so on its own page, in the tools it declares. 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.