Everpod

Start a pod

start_pod

Idempotent

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 kind now asked for.

Input Schema

Name	Required	Description
`kind`	No	Which kind of pod: 'developer', a cloud computer its owner runs, with their pick of Claude Code, Codex, OpenCode, Pi, Hermes and OpenClaw installed, or 'openclaw', OpenClaw set up and run for you on a computer of its own, the default when left out. OpenClaw among a developer pod's agents is the same agent installed for the owner to run themselves, not the OpenClaw pod.
`name`	Yes	The name the owner wants: their agent's name for an OpenClaw pod, the machine's name for a developer pod, where it is also the machine's name on their network, so a short plain word. Up to 40 characters.
`size`	No	For a developer pod: its size, as the owner chooses: 's' (4 vCPU, 8 GB, 80 GB, room for about 8 coding agents at once), 'm' (8 vCPU, 16 GB, 160 GB, room for about 16 coding agents at once), 'l' (16 vCPU, 32 GB, 320 GB, room for about 32 coding agents at once). Leave it out for the S. Ask the owner which they want; each size's price is on https://everpod.ai/developer-pod.
`login`	No	For a developer pod, where it is needed: the username its owner will have on the machine, such as alex. Lowercase letters and numbers, starting with a letter.
`agents`	No	For a developer pod: which coding agents come installed, as the owner chooses, one or more of 'claude' (Claude Code), 'codex' (Codex), 'opencode' (OpenCode), 'pi' (Pi), 'hermes' (Hermes) and 'openclaw' (OpenClaw). Leave it out and Claude Code and Codex come installed. Ask the owner which they want.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 9, 2026

changedInput schema / properties / agents / description

Previous value: -"For a developer pod: which coding agents come installed, as the owner chooses, one or more of 'claude' (Claude Code), 'codex' (Codex), 'opencode' (OpenCode) and 'pi' (Pi). Leave it out and Claude Code and Codex come installed. Ask the owner which they want."New value: +"For a developer pod: which coding agents come installed, as the owner chooses, one or more of 'claude' (Claude Code), 'codex' (Codex), 'opencode' (OpenCode), 'pi' (Pi), 'hermes' (Hermes) and 'openclaw' (OpenClaw). Leave it out and Claude Code and Codex come installed. Ask the owner which they want."

changedInput schema / properties / agents / items / enum

Previous value: -[
-  "claude",
-  "codex",
-  "opencode",
-  "pi"
-]New value: +[
+  "claude",
+  "codex",
+  "opencode",
+  "pi",
+  "hermes",
+  "openclaw"
+]

changedInput schema / properties / kind / description

Previous value: -"Which kind of pod: 'developer', a cloud computer its owner runs, with their pick of Claude Code, Codex, OpenCode and Pi installed, or 'openclaw', a managed OpenClaw agent on a computer of its own, the default when left out."New value: +"Which kind of pod: 'developer', a cloud computer its owner runs, with their pick of Claude Code, Codex, OpenCode, Pi, Hermes and OpenClaw installed, or 'openclaw', OpenClaw set up and run for you on a computer of its own, the default when left out. OpenClaw among a developer pod's agents is the same agent installed for the owner to run themselves, not the OpenClaw pod."

Changed3 schema fields changedOct 9, 2026

changedInput schema / properties / agents / description

Previous value: -"For a developer pod: which coding agents come installed, as the owner chooses: ['claude'] for Claude Code, ['codex'] for Codex, or both. Leave it out and both come installed. Ask the owner which they want."New value: +"For a developer pod: which coding agents come installed, as the owner chooses, one or more of 'claude' (Claude Code), 'codex' (Codex), 'opencode' (OpenCode) and 'pi' (Pi). Leave it out and Claude Code and Codex come installed. Ask the owner which they want."

changedInput schema / properties / agents / items / enum

Previous value: -[
-  "claude",
-  "codex"
-]New value: +[
+  "claude",
+  "codex",
+  "opencode",
+  "pi"
+]

changedInput schema / properties / kind / description

Previous value: -"Which kind of pod: 'openclaw' (the default), a managed OpenClaw agent on a computer of its own, or 'developer', a cloud computer its owner runs, with Claude Code, Codex or both installed."New value: +"Which kind of pod: 'developer', a cloud computer its owner runs, with their pick of Claude Code, Codex, OpenCode and Pi installed, or 'openclaw', a managed OpenClaw agent on a computer of its own, the default when left out."

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / size

Added value: +{
+  "description": "For a developer pod: its size, as the owner chooses: 's' (4 vCPU, 8 GB, 80 GB, room for about 8 coding agents at once), 'm' (8 vCPU, 16 GB, 160 GB, room for about 16 coding agents at once), 'l' (16 vCPU, 32 GB, 320 GB, room for about 32 coding agents at once). Leave it out for the S. Ask the owner which they want; each size's price is on https://everpod.ai/developer-pod.",
+  "enum": [
+    "s",
+    "m",
+    "l"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / agents

Added value: +{
+  "description": "For a developer pod: which coding agents come installed, as the owner chooses: ['claude'] for Claude Code, ['codex'] for Codex, or both. Leave it out and both come installed. Ask the owner which they want.",
+  "items": {
+    "enum": [
+      "claude",
+      "codex"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / kind / description

Previous value: -"Which kind of pod: 'openclaw' (the default), a managed OpenClaw agent on a computer of its own, or 'developer', a cloud computer its owner runs, with Claude Code and Codex installed."New value: +"Which kind of pod: 'openclaw' (the default), a managed OpenClaw agent on a computer of its own, or 'developer', a cloud computer its owner runs, with Claude Code, Codex or both installed."

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, but the description adds genuinely non-obvious behavior: no charge occurs at call time, the pod stays unpaid until pay_url is opened in a browser, and a repeat call returns the same pod renamed/retyped rather than creating another.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loading the verb and the kind split before the billing/idempotency caveat; no filler, though the billing sentence and the repeat-call sentence could be merged without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully surfaces the pay_url return and the unpaid-pod state an agent needs to act on; a mutation tool with no annotations gap here, though it omits auth/permission requirements and what the immediate response contains besides pay_url.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each field (kind, name, size, login, agents) is richly documented in the schema itself, so a baseline 3 is appropriate; the description only echoes the 'developer' kind distinction without adding syntax or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start a new pod for the owner') and immediately bifurcates the two pod kinds, so an agent can tell it apart from get_pod/list_pods which only read existing pods.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (create a pod, pay later) and the repeat-call behavior is described, but the description never says when to reach for this versus get_pod/list_pods, nor any precondition about an existing pod or owner state required before starting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Everpod tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Start a pod

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources