For developers

Your agent can already write good code. beam.page is where it ships.

Static hosting + MCP + REST API, with a small set of features picked for agents shipping real sites. Snapshot / rollback. Per-project subdomains. Zero build step.

Connect your agent Tool surface →

A silver laptop on a desk with a prism-triangle beam.page sticker on the lid; a monitor behind shows an outline of MCP, REST API, static hosting, and AI-agent-driven development

What is it?

beam.page hosts static sites and SPAs on per-project subdomains (your-slug.beam.page). Drive it from any MCP-compatible agent at https://api.beam.page/mcp, or hit the REST API directly at api.beam.page. Bring any stack that runs in the browser — Tailwind + Alpine are the defaults, but React builds, htmx, or plain HTML all work.

The approach

We're trying to make publishing static sites and SPAs from an AI agent as easy as it should be. Every feature is picked deliberately — agent-native tool names, snapshot and rollback, per-project subdomains with HTTPS, structured metadata, a built-in form-to-email action, self-describing docs at /llm.txt. If something makes a real difference to shipping, it's in. If it's ceremony, it isn't.

We listen to feedback from the agents using the platform and keep the surface small on purpose. If you've got thoughts, the feedback MCP tool sends them straight to us.

Connect your agent

Same setup as every other user. One URL in, one Google login, done.

https://api.beam.page/mcp

Per-client install steps →

Tool surface

Fifteen MCP tools, each named for the action it performs. Full spec at beam.page/llm.txt.

Tool	What it does
`whoami`	Current caller's profile, limits, usage, account type.
`project`	Create / list / get / update / delete projects (microsites).
`page`	Create / list / get / update / delete sub-pages within a project.
`upload_text`	Upload HTML / CSS / JS / JSON / SVG / TXT inline or via public URL.
`upload_binary`	Upload images, PDFs, fonts via presigned S3 PUT.
`upload_zip`	Upload a whole bundle of files at once (SPA builds, galleries).
`read_content`	Read a page's files, a project's assets, or a specific file back.
`edit`	Surgical find-and-replace inside existing files.
`delete_content`	Delete a file, an asset, or a sub-page.
`redirect`	Create / list / delete project-scoped redirects.
`snapshot`	List / get / take / restore project snapshots (rollback).
`fetch_live`	Fetch the CDN-served content (verify what users see, bypass cache).
`feedback`	Submit platform feedback straight from an agent session.
`guide`	Onboarding + reference topics (orient, actions, conventions, pitfalls).
`api`	Escape hatch — call any REST endpoint directly.

Full API reference →

Limits

No surprise quotas. Free tier today:

project / account

pages / project

assets / project

Platform caps (same across every tier):

• 10 files per page
• 4 MB per file
• 200 KB of structured metadata per page

Paid tiers (on the way) will raise the project, page, and asset limits. We'll publish the changes clearly — no fine print.

Pricing

Free today on <slug>.beam.page. Paid tiers with custom domains and higher quotas coming. See pricing →

Managing many sites

An account can hold several projects — 1 on the free tier today, more on paid tiers (coming). Your agent can spin up a new site in one call, update any of them from the same conversation, and roll any one of them back without touching the others.

Ready to ship?

Connect in your AI client

Building a site for a client or a shop? See the small-business view →