# Helipod

Integrates Helipod cloud infrastructure with your coding assistant to deploy apps, manage Postgres databases, and control virtual servers.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: helipodapp
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/helipodapp/mcp
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/helipod

## What it does

This server gives your AI assistant access to 229 infrastructure tools across containers, databases, virtual private servers, and domains. The assistant can trigger container builds from source code, inspect failing logs, configure routing, and handle transactional mail.

Clients connect either through the hosted HTTP endpoint at `https://api.helipod.io/mcp` or by running the `helipod-mcp` package on Node.js 18+. Domain operations will fail unless the `HELIPOD_API_KEY` token has account-wide permissions rather than single-project scope.

## Requirements
- Needs: Docker
- Remote server: `https://api.helipod.io/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http helipod https://api.helipod.io/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add helipod --url https://api.helipod.io/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "helipod": {
            "url": "https://api.helipod.io/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "helipod": {
            "type": "http",
            "url": "https://api.helipod.io/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http helipod https://api.helipod.io/mcp
```

## When to use it
- deploy a web application directly from Git
- provision an isolated Postgres database for a backend
- inspect build logs after a broken deployment
- set up domain DNS records for a live container

## Example prompts
- Deploy the current repository to my Helipod environment and return the public URL.
- Spin up a new Postgres instance and wire its credentials into the backend app.
- Check the build logs for the latest failed release to see what broke.

## Similar
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43902
- [Coder](https://affpapa.org/en/nevibecode/mcp/coder.md) — MCP server · ★ 17191
- [firebase-mcp](https://affpapa.org/en/nevibecode/mcp/firebase-mcp.md) — MCP server · ★ 4482
- [Radar Kubernetes MCP Server](https://affpapa.org/en/nevibecode/mcp/radar-kubernetes-mcp-server.md) — MCP server · ★ 3918
- [Supabase](https://affpapa.org/en/nevibecode/mcp/supabase.md) — MCP server · ★ 2974
- [Microsoft Fabric MCP Server](https://affpapa.org/en/nevibecode/mcp/microsoft-fabric-mcp-server.md) — MCP server · ★ 3804

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md