Agent hosting platforms compared (2026)
Seven platforms an AI agent can turn a file into a URL through, set beside each other on the things that decide whether the agent finishes inside one turn. Vercel reaches furthest. NudgeHost asks for the least before the first call.
Figures last verified 6 September 2026
- 2 of 7publish without an account
- 5 of 7publish an MCP server
- 1 of 7carries the API and MCP on a free plan
An agent that has produced something needs a URL for it before the turn ends, and the seven platforms below answer that in different orders. NudgeHost gives an AI client four tools over Streamable HTTP, so it can publish an HTML page and hand the link back inside the same conversation. The four REST endpoints and the tool schemas are written out in the API reference.
Vercel is the strongest entrant here. Their MCP server at mcp.vercel.com is remote and OAuth, implements the MCP Authorization and Streamable HTTP specifications, and covers documentation search, project and deployment management, deployment log analysis and Web Analytics queries. Their changelog states that it can now deploy code and that it supports purchases, which is closer to publishing from inside a conversation than anything else in the table. Twelve clients are approved for it, among them Claude Code, ChatGPT, Codex CLI, Cursor and VS Code with Copilot, and only reviewed and approved clients may connect.
What separates the two is the ground underneath a publish. NudgeHost runs the API and the MCP server from the free plan, at 2 keys and 20 requests a minute, with no credit meter behind a publish and no account before the first one. Vercel wants a platform account with a project behind it. Netlify meters in credits, 15 for a production deploy against a free plan that is a hard limit of 300 credits a month, and their FAQ states that one project over its limit pauses all projects on the account.
What each one needs before it can start
The two questions that decide most of it, across all seven. Everything else is in the cards below.
| Platform | What has to exist before the first call | What reaching the API or MCP server takes |
|---|---|---|
| NudgeHost | Nothing. No project, no repository, and no account before the first publish | The free plan, at 2 keys and 20 requests a minute |
| Vercel | A platform account with a project behind the deployment | Public MCP tools answer without authentication, and the authenticated tools need it |
| Netlify | A project. Drop makes a temporary one for a dragged folder, claimed within an hour | Their free plan is a hard limit of 300 credits a month |
| GitHub Pages | An account, a repository and a commit | The REST API reaches repositories and Pages |
| Static.app | An account, and a website on the plan | Starter, their first paid plan, at $6 a month or $5 a month billed annually at $60 a year |
| Tiiny.host | An account and a verified email | Solo, their second paid tier. The entry paid plan is $9 a month, or $5 a month billed annually at $60 a year |
| Linkyhost | An account | Enterprise, at $199 a year |
The full answer, one card each
Open the ones you are weighing. A question a vendor publishes nothing on is left out rather than answered for them.
NudgeHostLeast to start
- What has to exist before the first call
- Nothing. No project, no repository, and no account before the first publish
- An MCP server
- Four tools over Streamable HTTP, on an OAuth 2.0 protected resource publishing RFC 9728 metadata
- What it reaches, and who may connect
- Create an upload URL, complete the upload, share text, list links. Any client that speaks Streamable HTTP and OAuth 2.0
- How a publish is made
- A signed URL from the API, the bytes by PUT, then a complete call. Text goes inline through
share_textand comes back as a link in one call - What the input can be
- Any file's bytes, or text inline up to 2MB of UTF-8. A filename ending .html renders in the browser
- What reaching the API or MCP server takes
- The free plan, at 2 keys and 20 requests a minute
- What is metered behind a publish
- Nothing per publish. 20 API requests a minute is the free ceiling
- How long a signed-out publish lives
- 7 days, on 3 links at 25MB each, claimable later by signing up
VercelReaches furthest
- What has to exist before the first call
- A platform account with a project behind the deployment
- An MCP server
mcp.vercel.com, remote and OAuth, on the MCP Authorization and Streamable HTTP specifications- What it reaches, and who may connect
- Documentation search, project and deployment management, deployment log analysis and Web Analytics queries, and their changelog says it can now deploy code and supports purchases. Twelve approved clients, and only reviewed and approved ones may connect
- How a publish is made
- Their changelog states that the MCP server can now deploy code
- What the input can be
- Code
- What reaching the API or MCP server takes
- Public MCP tools answer without authentication, and the authenticated tools need it
- How long a signed-out publish lives
- Nothing publishes signed out
NetlifyRuns the agent for you
- What has to exist before the first call
- A project. Drop makes a temporary one for a dragged folder, claimed within an hour
- An MCP server
- Yes, with agent documentation at
netlify.ai - What it reaches, and who may connect
- Agent Runners that execute Claude Code, OpenAI Codex and Google Gemini from the dashboard, where a run that changes a file generates a Deploy Preview
- How a publish is made
- A deploy through their API, from a file digest or a ZIP. Drop takes a dragged folder
- What the input can be
- A file digest, a ZIP, or a dragged folder
- What reaching the API or MCP server takes
- Their free plan is a hard limit of 300 credits a month
- What is metered behind a publish
- Credits. 15 a production deploy, 20 a GB of bandwidth, 2 per 10,000 web requests, against 300 free a month. A project at its limit pauses, and their FAQ says one project over its limit pauses all projects on the account
- How long a signed-out publish lives
- One hour. The anonymous deploy is a temporary project and has to be claimed inside it
GitHub PagesBeside the code
- What has to exist before the first call
- An account, a repository and a commit
- An MCP server
github/github-mcp-server, remote and local, generally available since 4 September 2025- What it reaches, and who may connect
- Repositories, issues, pull requests, Actions and code scanning, from the remote server or a local one
- How a publish is made
- A commit, then the Jekyll pipeline or an Actions workflow
- What the input can be
- Files committed to a repository
- What reaching the API or MCP server takes
- The REST API reaches repositories and Pages
- What is metered behind a publish
- Published sites up to 1GB, a soft limit of 10 builds an hour, a soft bandwidth limit of 100GB a month, and deployments that time out after 10 minutes
- How long a signed-out publish lives
- Nothing publishes signed out
Static.app
- What has to exist before the first call
- An account, and a website on the plan
- An MCP server
- Listed from Starter, their first paid plan
- How a publish is made
- Through the API listed from Starter
- What the input can be
- A website, at 50MB of storage on the free plan
- What reaching the API or MCP server takes
- Starter, their first paid plan, at $6 a month or $5 a month billed annually at $60 a year
- What is metered behind a publish
- One website at 50MB of storage on the free plan
- How long a signed-out publish lives
- Nothing publishes signed out
Tiiny.host
- What has to exist before the first call
- An account and a verified email
- An MCP server
- A REST API
- How a publish is made
- Through the API listed from Solo
- What reaching the API or MCP server takes
- Solo, their second paid tier. The entry paid plan is $9 a month, or $5 a month billed annually at $60 a year
- How long a signed-out publish lives
- Nothing publishes signed out
Linkyhost
- What has to exist before the first call
- An account
- An MCP server
- A REST API
- How a publish is made
- Through the API listed on Enterprise
- What reaching the API or MCP server takes
- Enterprise, at $199 a year
- How long a signed-out publish lives
- Nothing publishes signed out
Competitor figures read from each vendor’s own documentation and pricing pages on 5 and 6 September 2026. Vercel’s MCP documentation carries a last-updated date of 13 August 2026. NudgeHost figures come from the current plan definitions.
Which one to reach for
NudgeHost
When a file has to become a URL now and nothing should have to exist first. Signed out it takes 25MB a file and 3 links at once, each running 7 days and claimable later by signing up, and the free plan then carries 2 API keys at 20 requests a minute with no credits counted against a publish.
Vercel
When the agent's work is code and the project already exists there. Their MCP server reaches further than anything else in this table, and their changelog says it can deploy.
GitHub Pages
When the artifact belongs in a repository anyway, and a commit, a build and a ten minute deployment ceiling are steps worth taking.
Five of the platforms above have a page of their own here, and the NudgeHost and Netlify Drop comparison takes the Netlify row apart figure by figure, or you can compare file-sharing tools one at a time.
Frequently asked questions
Which of these can an agent publish through without an account?
NudgeHost and Netlify Drop. NudgeHost takes 25MB a file signed out, 3 links at once, each running 7 days and claimable later by signing up. Netlify Drop publishes a dragged folder logged out, but the anonymous deploy is a temporary project and has to be claimed within one hour. Vercel, GitHub Pages, Static.app, Tiiny.host and Linkyhost all want an account first, and Tiiny.host wants a verified email with it.
Which platform has the most capable MCP server?
Vercel. Theirs is remote and OAuth, implements the MCP Authorization and Streamable HTTP specifications, and covers documentation search, project and deployment management, deployment log analysis and Web Analytics queries. Their changelog states that it can now deploy code and that it supports purchases. Twelve clients are approved for it, and only reviewed and approved clients may connect. The NudgeHost server is four tools and does one job, turning a file or a block of text into a public link, and any client that speaks Streamable HTTP and OAuth 2.0 can use it.
What does a publish cost on each of them?
NudgeHost charges nothing for it on the free plan and counts no credits against it, with 20 API requests a minute as the ceiling. Netlify spends 15 credits on a production deploy against a free plan that is a hard limit of 300 credits a month, with bandwidth at 20 credits a GB and web requests at 2 credits per 10,000. GitHub Pages charges nothing and caps published sites at 1GB, with a soft limit of 10 builds an hour and a soft bandwidth limit of 100GB a month. The Static.app free plan is one website at 50MB of storage, with a free subdomain and SSL.
Which plan does the API start on?
The free one on NudgeHost, at 2 keys and 20 requests a minute. Static.app lists API and MCP access from Starter, their first paid plan, at $6 a month or $5 a month billed annually at $60 a year. Tiiny.host lists the API from Solo, their second paid tier, and their entry paid plan is $9 a month or $5 a month billed annually at $60 a year. Linkyhost publishes API access on Enterprise at $199 a year.
What happens when a free plan runs out?
On Netlify a project at its limit pauses, and their FAQ states that one project over its limit pauses all projects on the account. GitHub Pages describes its 10 builds an hour and its 100GB a month as soft limits. NudgeHost refuses the call above 20 requests a minute and leaves every published link serving.
See for yourself
The free plan is genuinely free. Try it before you decide.
Get started free