# Everpod [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/everpod-ai/mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/everpod

## Description
Your own AI agent on an always-on cloud computer: Claude Code, Codex and more, or managed OpenClaw.

## Tools
Capabilities this server exposes over MCP:

- **list_pods** — List the pods on the owner's Everpod account, oldest first. Each has its kind, its status and the link its owner needs: pay_url while it is awaiting payment, url (the pod's page on everpod.ai) once it is paid.
- **get_pod** — Read one pod by its id: its status and the link its owner needs. This is how to check whether a started pod has been paid for, whether it is ready, and for a developer pod, which of its owner's steps to connect it are done.
- **start_pod** — Start a new pod for the owner: an OpenClaw pod, or with kind 'developer' a developer pod. This call charges nothing: the pod stays unpaid until its owner opens pay_url in their browser and pays there. While the account has an unpaid pod, calling again returns that same pod, changed to the name and…

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "everpod": {
    "url": "https://everpod.ai/mcp"
  }
}
```

## Documentation

## What Everpod MCP server does

Everpod MCP server gives an existing MCP client access to a small set of account and pod operations on Everpod. It is intended for managing cloud computers associated with the authenticated account, rather than controlling the machine after it has been created.

The available pod types are OpenClaw and developer. An agent can request a new pod, receive the payment link, and later inspect its status. Starting a pod does not charge the account. The owner must open the supplied payment link and complete payment on everpod.ai. If an unpaid pod already exists, another start request returns that pod and applies the newly requested name and kind.

## How it works

The service is hosted at `https://everpod.ai/mcp`, so there is no local package or process to install. An MCP client connects over HTTP and authenticates each request with an Everpod API key in the `Authorization: Bearer YOUR_KEY` header.

Everpod MCP server exposes three operations:

- `list_pods` returns the account's pods in oldest-first order, including each pod's kind, status, and the relevant account link.
- `get_pod` reads one pod by ID. Its response helps determine whether payment is complete, whether the pod is ready, and which developer-pod connection steps have been completed.
- `start_pod` requests an OpenClaw pod or, when `kind` is `developer`, a developer pod.

The service does not let the key pay for a pod, modify or cancel a plan, delete resources, open an agent control panel, or access the machine belonging to a developer pod.

## Setup and configuration

Create a key at `everpod.ai/account/keys` by signing in with an email address and the code sent to it. Configure the MCP client with the hosted URL and the key header. For Codex, the documented setup stores the key in `EVERPOD_API_KEY` and passes that variable as the bearer-token source. Other clients can use an equivalent environment-variable reference in their MCP configuration.

Claude Code, Codex, and OpenClaw have documented connection commands. OpenClaw can also install the Everpod skill, while Claude Code and Codex can install the developer-pod skill from the Everpod skills repository. The skills provide additional instructions for completing the user-controlled steps needed to open a developer pod.

## Tools and capabilities

Everpod MCP server is suitable for agents that need to discover existing pods, track a pod after creation, or tell an owner where payment and account actions must occur. Its REST operations are also available through Everpod's JavaScript and Python client libraries.

A developer pod can be prepared from an initial request through the remaining connection steps, but the owner performs those steps. The MCP tools report progress; they do not provide direct access to the developer pod's machine.

## Limitations and notes

Payment remains an interactive browser action on everpod.ai. The MCP key cannot pay, change or cancel a plan, delete anything, open the agent's control panel, or reach a developer pod's computer. Pod readiness and developer connection progress should be checked with `get_pod` after creation or payment. The material does not describe local hosting, configurable server settings, or additional MCP tools.

_Full upstream README: https://allmcps.com/mcp/everpod/readme_