Overview
agenthost is web hosting your agent drives. Connect it once, then ask for a link. Start here for the guides, the deploy reference, or the full MCP tool surface.
agenthost is web hosting your agent drives. You connect it to Claude, Claude Code, Cursor or any other MCP client once, and from then on putting something online is a sentence: "put this online." There is no dashboard to learn and nothing to configure first.
These docs are written for two readers, and they say which is which.
I made something and want it online
Plain language, no jargon. What agenthost is, how to connect your agent, and how to get your first link.
I'm deploying (or I'm the agent)
The contract: the entrypoint each runtime looks for, how the runtime is chosen, and how to confirm a deploy actually serves.
How this is organised
| Section | What's in it |
|---|---|
| Getting started | What agenthost is, connecting your agent, your first link, and the words we use. |
| How-to | One page per task: a website, an app, your own domain, private access, teammates, fixing a broken deploy. |
| Deploy | What agenthost expects from your source: runtimes, entrypoints, versions, environment, and how to confirm a deploy. |
| Your account | Signing in, roles and organizations, and how plans count what you host. |
| Tool reference | Every tool the MCP exposes, grouped by what it acts on. Its own tab, up top. |
Start here
What agenthost is
What you need, what you can put online, and what you never have to learn.
Connect your agent
One click or one command, then sign in with your email. About three minutes.
Your first deploy
From connected to a live link, and how to tell it actually worked.
How-to guides
One page per task: a website, an app, your own domain, private access, teammates, fixing a broken deploy.
Deploying, in 60 seconds
The runtime decides how your source is built and started. Each looks for one entrypoint:
| Runtime | Inferred from | Entrypoint it looks for | Installs deps from |
|---|---|---|---|
static | index.html | index.html at the project root | — |
node | package.json | npm start (the start script) | package.json |
python | requirements.txt, .py | app imported from app.py | requirements.txt |
php | composer.json, .php | index.php at the project root | composer.json (optional) |
Builds are asynchronous: a successful call means queued, not live. Poll get_app until the status
settles, then confirm with a real request. There is no start-command and no port setting — how an app
starts is the convention above, and an undefined field is silently ignored rather than rejected.
The whole contract is in the deploy reference.
These docs are readable as plain markdown
Every page is served as markdown at the same path under /llms.mdx/docs, and there's a
/llms.txt index of the lot. The copy button at the top of each page hands you that markdown
directly — useful for pasting a page into an agent that isn't connected yet.