Your agent’s persistent teammate

Connect it One command

Create an MCP token on the dashboard (Account → MCP keys), then from any machine running Claude Code:

claude mcp add --transport http ergod https://app.ergod.dev/mcp \
  --header "Authorization: Bearer <your token>"

Any editor client that sends a bearer header works the same way — the endpoint is POST https://app.ergod.dev/mcp. Without a token the server answers a proper 401 handshake, so a client that supports it will walk you to connecting.

Five tools, not forty Small on purpose

Big MCP servers spend tens of thousands of tokens of your context on tool definitions before you type anything. Ergod deliberately exposes five: run_task starts work in your hosted workspace and returns a handle immediately; get_task_status polls it, and while the task runs it reports what the agent is doing and the tail of its output so far; list_artifacts lists what the workspace holds; get_artifact fetches a file — inline when it fits, as a revocable download link when it doesn’t; and deliver_result posts a finished result into your own DM or a Discord channel you’re a member of — the last mile no delegation API does.

Not a sandbox API

Renting isolated vCPUs is a solved, cheap market — that is not what this is. The unit here is a finished task by an agent that keeps your workspace between calls, remembers you across sessions, and knows where your people are. Delegate, poll, pull the files back — or just say “deliver it to the channel.”

Your same budget

No new pricing. An MCP task is an ordinary turn against your existing tier’s usage, metered exactly like a Discord or browser turn, and when the budget runs out the task fails with a machine-readable QUOTA_EXHAUSTED your agent can branch on instead of retrying into a wall.

One workspace, every surface

The workspace your agent delegates into is the same one behind Discord, Telegram and the dashboard. A file a task produced is already in your file browser, already attachable in a channel, already shareable on a public link you can revoke.

Honest constraints Read before wiring

Static bearer tokens, not OAuth — which means editor clients work today and the claude.ai / ChatGPT connector directories don’t, yet. Tasks are poll-based: no push, no streams, by the current protocol revision’s own design. One container per account, up to three tasks in flight, and the container idles out between calls (10 minutes on Free, 60 on paid) — files survive that, running processes don’t. Large or binary results come back as links rather than inline, because your client’s tool-result ceiling is real. Tokens mint no identity: every call is scoped to the account that minted the token, and there is no argument in any tool for naming somebody else’s.

Where this fits

Ergod is an MCP client too — it connects out to your servers and uses their tools in its own loop. That direction has its own page, and the technical breakdown covers the sandbox, the tool inventory and the limits underneath both.