InfraOps MCP Server
Enables infrastructure operations through Claude Code by exposing 195 tools across 7 providers including Coolify, VPS, Hetzner, Namecheap, Cloudflare, Supabase, and GitHub for server management, DNS, cloud resources, and more.
README
InfraOps MCP Server
A Model Context Protocol server that exposes infrastructure operations as callable tools for Claude Code. Runs locally over stdio — no HTTP server, no container, no remote deployment.
This is the "doer." For infrastructure standards and deployment patterns
see the infra-brain MCP. For application-level context see app-brain.
Providers
| Provider | Prefix | Tools | Always on | Required env |
|---|---|---|---|---|
| Coolify | coolify_ |
67 | ✅ | COOLIFY_PROD_BASE_URL + COOLIFY_PROD_API_TOKEN |
| VPS (SSH/orb) | vps_ |
7 | ✅ | — (defaults route to Hetzner prod) |
| Hetzner Cloud | hetzner_ |
26 | ❌ | HETZNER_API_TOKEN |
| Namecheap | namecheap_ |
19 | ❌ | NAMECHEAP_API_USER + NAMECHEAP_API_KEY + NAMECHEAP_PROXY_TOKEN |
| Cloudflare | cloudflare_ |
44 | ❌ | CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID |
| Supabase | supabase_ |
28 | ❌ | SUPABASE_ACCESS_TOKEN |
| GitHub | github_ |
4 | ❌ | GITHUB_TOKEN |
195 tools across 7 providers. Coolify and VPS register unconditionally; optional providers register only when their env vars are present at startup.
Coolify and VPS tools both accept an instance: "prod" | "dev" parameter
that routes between the Hetzner production VPS and a local OrbStack dev VM.
Tool implementations live in src/tools/ — schemas are defined inline via
Zod in each tool file.
Quickstart
npm ci
npm run build
npm test # vitest, 15 tests
The server is launched by Claude Code as a subprocess via start.sh, which
fetches secrets from Bitwarden Secrets Manager (BWS) and execs
node dist/index.js. To run it standalone (e.g. for debugging), invoke
start.sh from a shell that has BWS_ACCESS_TOKEN set.
Where to Look
| Document | What's in it |
|---|---|
CLAUDE.md |
Architecture map, patterns, per-provider notes, private-repo deploy workflow, compose app config, secrets policy. The canonical "how this works" doc. |
RUNBOOK.md |
Local setup, dev workflow, CI/CD, provider configuration, secret management, .claude.json example, troubleshooting. The canonical "how do I use/debug this" doc. |
BACKLOG.md |
Deferred work with full context — threat models, tradeoffs, acceptance criteria — designed to be resumed cold in a future session. |
INFRAOPS_IMPROVEMENTS.md |
Historical design doc for the v3.2.0 deploy-key / GitHub / compose work. Retained as context. Most items shipped; one remains open and is tracked in BACKLOG.md. |
Versioning
Current version: 3.3.0 (see package.json). Minor bumps track
user-visible tool API surface changes (new tools, new parameters); patch
bumps track bug fixes. CI runs tsc as the type-check gate on every push
to main via .github/workflows/build.yml.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.