InfraOps MCP Server
Provides 44 tools for managing Cloudflare services, including DNS, Pages, and other cloud resources.
Provides 4 tools for interacting with GitHub, enabling management of repositories and related resources.
Provides 26 tools for managing Hetzner Cloud resources such as servers, networks, and more.
Provides 19 tools for managing Namecheap domains and DNS settings.
Provides 28 tools for interacting with Supabase projects, managing databases, authentication, and other backend services.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@InfraOps MCP Serverlist my Hetzner cloud servers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| 67 | ✅ |
|
VPS (SSH/orb) |
| 7 | ✅ | — (defaults route to Hetzner prod) |
Hetzner Cloud |
| 26 | ❌ |
|
Namecheap |
| 19 | ❌ |
|
Cloudflare |
| 44 | ❌ |
|
Supabase |
| 28 | ❌ |
|
GitHub |
| 4 | ❌ |
|
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.
Related MCP server: Coolify MCP Tools
Quickstart
npm ci
npm run build
npm test # vitest, 15 testsThe 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 |
Architecture map, patterns, per-provider notes, private-repo deploy workflow, compose app config, secrets policy. The canonical "how this works" doc. | |
Local setup, dev workflow, CI/CD, provider configuration, secret management, | |
Deferred work with full context — threat models, tradeoffs, acceptance criteria — designed to be resumed cold in a future session. | |
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 |
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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlobarQuest/infraops-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server