LetsCloud MCP Server

Unlike "local" MCP servers,this is a hosted service: any LetsCloud customer can connect by providing their API key —no installation required on the client side.

The same backend also exposes a cleanREST APIunder/api/v1for plain HTTP integrations (curl, scripts, automations).

- 🔌Native MCP transport(Streamable HTTP) at/mcp
- 🌐REST APIat/api/v1mirroring every MCP tool
- 🔑Per-request authenticationviaAuthorization: Bearer <api-key>
- 📦 Full coverage of the LetsCloud API — instances, SSH keys, snapshots, plans, images, locations, account
- ⚡ Async, fast and lightweight (FastAPI + httpx + official MCP SDK)
- 🐳 Docker-ready
- 📝 Auto-generated OpenAPI docs at/docs

┌──────────────────┐ Authorization: Bearer <api-key> ┌──────────────────────┐ │ AI client (MCP) │ ───────────────────────────────────────► │ mcp.letscloud.io/mcp │ │ Claude, Cursor… │ │ (this server) │ └──────────────────┘ └──────────┬───────────┘ │ api-token: <key> ▼ ┌──────────────────────────┐ │ core.letscloud.io/api │ └──────────────────────────┘

The user's API key never leaves the request: the server just relays it to the LetsCloud upstream and returns the response. The server itself stores no credentials.

Claude Desktop / Cursor / Windsurf (remote MCP)

{ "mcpServers": { "letscloud": { "url": "https://mcp.letscloud.io/mcp", "headers": { "Authorization": "Bearer YOUR_LETSCLOUD_API_KEY" } } } }

Note: the exact field names may differ slightly between clients (some usetransport: "streamable-http", others auto-detect). Check your client's docs for "remote MCP server".

curl -H "Authorization: Bearer YOUR_LETSCLOUD_API_KEY" \ https://mcp.letscloud.io/api/v1/account

curl -H "Authorization: Bearer YOUR_LETSCLOUD_API_KEY" \ https://mcp.letscloud.io/api/v1/instances

Full interactive docs (with request/response schemas) are available at/docs.

Every request to/mcpand/api/v1/*must carry the user's LetsCloud API key inoneof:

- Authorization: Bearer <api-key>(recommended, MCP-friendly)
- X-LetsCloud-Token: <api-key>(fallback)

src/letscloud_mcp/ ├── main.py # FastAPI app, mounts /mcp and /api/v1 ├── __main__.py # uvicorn entrypoint (python -m letscloud_mcp) ├── config.py # Settings via pydantic-settings ├── auth.py # Per-request token extraction (ContextVar) ├── logging_setup.py # structlog ├── letscloud/ │ ├── client.py # Async httpx client for core.letscloud.io │ ├── models.py # Pydantic models (Profile, Instance, Snapshot…) │ └── exceptions.py ├── mcp_app/ │ ├── server.py # FastMCP server (Streamable HTTP) │ └── tools.py # @mcp.tool functions └── rest/ └── routes.py # FastAPI router for /api/v1

Core AWS MCP server providing prompt understanding and server management capabilities.

An AI-powered interface for managing the Dokploy infrastructure platform.

An AI-powered interface for managing the Dokploy infrastructure platform.

The official Impreza Host connector for offshore server management

Manage Railway infrastructure through natural language using the Railway API.

A remote Model Context Protocol (MCP) server for managing VPS servers and domains on Sitequest. Lets AI assistants provision, monitor, and configure infrastructure through natural language.

Manage your Bedrock server with natural language commands using the Bedrock Server Manager API.

Manage and interact with Microsoft Azure services.

An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.