Documentation

Elestio MCP Server

Connect any MCP-compatible AI to the full Elestio DevOps platform. Deploy services, manage billing, configure backups, monitor logs — all from natural language conversations with Claude, ChatGPT, Cursor, and other AI tools.

Server URL: https://mcp.elest.io/


# What is Elestio MCP?

The Elestio MCP server exposes 68 tools that map directly to the Elestio API. Once connected, your AI client can:

The server is built on the Model Context Protocol (MCP) standard, with OAuth 2.1 + PKCE for secure authentication.


# Quick start

  1. Open your AI client (Claude.ai, ChatGPT, Cursor, etc.)
  2. Add a remote MCP server with the URL https://mcp.elest.io/
  3. Click Authorize when the consent screen appears
  4. Log in with your Elestio email + API token

Once authorized, the AI can call any of the 68 tools on your behalf.


# Connect to your AI client

# Claude.ai (web, Pro/Team plan)

  1. Open Claude.ai → click your avatar → SettingsConnectors.
  2. Click Add custom connector.
  3. Paste the URL: https://mcp.elest.io/
  4. Click Connect → the Elestio consent page opens in a new tab.
  5. Enter your Elestio email + API token (get one from dash.elest.io → Account → API tokens).
  6. Click Authorize.

The connector now appears in every conversation. Mention "Elestio" in your prompt and Claude will use the tools automatically.

# Claude Code (CLI)

claude mcp add elestio https://mcp.elest.io/

The CLI walks you through OAuth in your browser. After authorization, run claude normally — /mcp shows the registered server and tool count.

# ChatGPT (custom connector)

ChatGPT supports remote MCP servers via the Connectors feature (Plus/Pro/Team plans).

  1. In ChatGPT → SettingsConnectorsAdd a custom connector.
  2. Name: Elestio
  3. MCP server URL: https://mcp.elest.io/
  4. Authorization: OAuth (default)
  5. Click Save → ChatGPT opens the consent screen.
  6. Authorize with your Elestio email + API token.

In any conversation, enable the Elestio connector from the connector menu before prompting.

# Cursor

Open ~/.cursor/mcp.json (create it if missing) and add:

{
  "mcpServers": {
    "elestio": {
      "url": "https://mcp.elest.io/"
    }
  }
}

Restart Cursor. The first call to an Elestio tool triggers the OAuth flow in your browser.

# Other clients (Windsurf, Continue, Zed, etc.)

Any MCP client supporting the Streamable HTTP transport with OAuth 2.1 + PKCE works out of the box. Point it at https://mcp.elest.io/ — the discovery endpoint at /.well-known/oauth-authorization-server advertises everything else.


# Authentication

This is the default flow used by all modern MCP clients. You never paste your API token into the AI client — instead, you authorize the MCP server once via a browser, and the client receives short-lived tokens (1h access, 30-day refresh, rotated).

# HTTP Basic auth (for scripts and headless clients)

If you're building a script or a server that doesn't have a browser, you can authenticate directly with an Elestio API token:

curl -X POST https://mcp.elest.io/ \
  -H "Authorization: Basic $(echo -n '[email protected]:YOUR_API_TOKEN' | base64)" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

Use this for CI/CD jobs, monitoring scripts, or backend services where OAuth is impractical.


# Tools reference

The 68 tools are grouped into 12 categories. Click the category to jump to the tools list.

# Account & discovery (3)

# Projects (4)

# Services (19)

# Billing (2)

# Firewall (3)

# SSL & Custom Domains (3)

# SSH Keys (3)

# System & application updates (4)

# Backups (8)

# Snapshots (4)

# Volumes (5)

# CI/CD pipelines (10)


# Troubleshooting

# "Session expired, restart authorization"

The OAuth consent page uses a signed session cookie. If you're authorizing from a browser where another tool (browser-automation, certain extensions) clears cookies between page loads, the session is lost.

Fix: Open the authorization link in a private/incognito window.

# "Invalid token" returned by the API

Two causes:

  1. Your Elestio API token has been revoked or expired — generate a new one in the dashboard and re-authorize.
  2. You're calling a tool with a wrong service or project ID. Elestio's API returns InvalidToken misleadingly when an ID doesn't belong to your account. Double-check the ID with list_services or list_projects.

# "Account not approved"

New Elestio accounts go through a quick approval step. Wait for the confirmation email, or contact [email protected].

# A tool call hangs or times out

# The MCP server returns 401

Your access token expired (1h lifetime). Most MCP clients refresh automatically. If yours doesn't:


# Resources


Last updated: 2026-05-12