Static-first edge delivery · MCP control plane

The deployment fabric for AI-built web.

Turn agent output into signed URLs, versioned releases, and live properties—without leaving the IDE. Built for teams who ship with Cursor, Claude, and whatever ships next Tuesday.

Best for SPAs, docs, marketing pages, and AI-generated micro-sites — anything that builds to static HTML/CSS/JS.

Yeah, we know handing deploy rights to a model via MCP is a bit unhinged.
However, we also know developers are lazy bastards.

Open console See live metrics

API + MCP surface
Staging → prod promote
Keyed automation

agent conversation

Operator UX that agents can drive end-to-end.

Try it out

Paste this into Cursor or Claude Code's `mcp.json`

Point it at your MCP endpoint, attach your API key, and your agent can deploy immediately. Don't worry, it won't screw up - we promise.

{
  "mcpServers": {
    "webprompter": {
      "url": "https://webprompter.ai/mcp",
    }
  }
}

Signal, not theater.

Real counts from this control plane. We could pad them like every other Series A deck, but the demo gods are watching.

Websites on platform 0 Provisioned properties ready to receive deploys.

Deployment events 0 Full pipeline history: every push through the edge.

Live edge slots 0 Current active + is_current serving traffic now.

Why angels stop scrolling.

Distribution where developers already live. Infrastructure they cannot duct-tape forever.

MCP is the new CLI

First-class Model Context Protocol—not a bolt-on webhook. Agents authenticate, upload artifacts, promote environments, and roll back with the same verbs your SREs would type—if they still had time.

AI-shaped release graph

Static sites explode in volume as codegen goes mainstream—SPAs, docs, marketing, AI-generated micro-sites. You win on versioned object storage, immutable deploys, and blast-radius—priced where hyperscalers are blind: the long tail of static builds.

Trust layer for agents

Per-key rate limits, revocable credentials, and audit-friendly trails. The missing governance layer for “the intern that never sleeps”—without killing velocity.

Minutes to revenue

Zip in, route to S3-backed edge, instant promote/rollback—opinionated paths that collapse weeks of glue into a single afternoon for a motivated founder (or an over-caffeinated model).

What “full stack” means here.

Identity Supabase-backed auth for humans; API keys for machines.
Artifacts Multer-hardened uploads, size caps, manifest validation before bytes touch the bucket.
Edge S3 + your public base URL—swap CloudFront, Fastly, or R2 without rewriting the product story.
Operations Deployment history, current pointers, and one-step rollback when every minute counts.

We are raising to own the agent-to-edge lane.

If you back teams betting on AI-first delivery and protocol-native infra, you already understand the wedge. Let’s talk cap table, GTM, and how fast this MCP surface compounds.