OpZero documentation
OpZero is a remote MCP server. You connect it to Claude once, with OAuth, and from then on your AI client can deploy real, live software on your behalf — web pages, AI-powered apps, assistants, your own hosted MCP servers, and gateways that tie them together.
What OpZero is
OpZero is not a REST API you write code against. It is a remote MCP server — a single HTTPS endpoint that speaks the Model Context Protocol. You add it to Claude the way you add any connector, authorize it with your OpZero account, and its tools become available inside your conversations.
There is nothing to install, no SDK to import, and no key to paste. You ask for what you want in plain language, Claude picks the tools, and OpZero does the building, hosting, and running.
https://opzero.sh/mcpStreamable HTTP transport, OAuth 2.1 with PKCE. Claude discovers everything else from /.well-known/oauth-protected-resource.
What you can build
The tool surface covers five kinds of thing, in roughly increasing ambition:
- Pages and sites. Markdown, themed HTML, multi-file sites, or React components — deployed to a live URL in one call. Tailwind classes are compiled for you.
- AI-powered apps. The same React deploy, with server-side inference and per-user storage switched on. Your app calls
window.claude.complete()andoz.storagewith no API keys of its own. - Assistants. A model, a pinned system prompt, and a set of MCP servers it can call as tools — deployed behind a chat endpoint your frontends can talk to.
- Hosted MCP servers. Write TypeScript or Python against the OpZero runtime and OpZero builds it, deploys it to a Worker, gives it a stable endpoint, and verifies it speaks MCP.
- Gateways and connections.Federate several MCP backends behind one endpoint, and give them OAuth’d access to third-party services like Notion or Linear.
How you actually use it
You do not call tools by name. You describe the outcome. A typical exchange looks like this:
“Put my Q3 notes up as a page I can send to the team.”
Calls deploy_markdown, hands back a live URL on your-page.opzero.sh.
The tool reference exists so you know what is possible and can ask precisely when you want to — not because you have to memorize it.
Which clients work
Claude — claude.ai, Claude Desktop, and Claude Code — is the supported path today, and the one these docs assume. Support for more MCP clients is coming.
Any client that speaks MCP over Streamable HTTP with OAuth can connect in the meantime; other clients covers Cursor, Codex, and raw HTTP, and mentions API keys for the automation cases where an interactive OAuth flow is not available.