Tool reference

The full tool catalogue with usage notes. Pass a topic to narrow it to one area or a single tool.

Your plan, usage, active projects, recent deployments, and how much of each per-plan cap is consumed. The cheapest way to confirm the connection works.

Ask a question about your own account in plain language. Answers over your recent activity, and renders an adaptive view on hosts that support MCP Apps.

Your token type, identity, roles, scopes, real session expiry, and the health of every OAuth discovery endpoint. Run this first on any auth error.

Prove your MCP client identity and your OpZero account are the same person. Returns a link URL to confirm in the browser. Required before a gateway backend may use an external connection.

Send raw markdown, get a themed page. Full GitHub-flavoured markdown, light/dark toggle, title lifted from the first heading. The lowest-effort way to publish.

Send body HTML, get it wrapped in the OpZero design system — glass nav, typography, colour palette. Standard HTML elements are styled for you.

Deploy one complete HTML document. Tailwind utility classes are compiled automatically, so no CDN script or config is needed.

Deploy a multi-file site — HTML, CSS, JS, assets — with full file-level control. Tailwind is still compiled for you.

Deploy a React component as a live site with zero build, via ESM.sh. React, Recharts, and Lucide are built in. Set ai and storage to turn it into a real application with a backend.

Ready-to-deploy starter files: the branded opzero theme (recommended), landing, portfolio, blog, static, vite-react, or react-esm.

Patch a live site by merging a partial file map into its latest deployment. Unmentioned files are preserved; an empty string deletes one.

Render one of your deployed pages inline in the conversation, on hosts that support MCP Apps. Identify it by URL, project ID, or project name.

An interactive widget showing your live site next to a prompt box. Edits typed there arrive back in the conversation, and the page hot-reloads once you apply them.

Everything you have deployed, with URLs and status. Filter by status, hosting target, name, or staleness.

One project by name or ID: metadata, current URLs, custom domain, status, and a summary of its latest deployment.

Create an empty project container. Usually unnecessary — the deploy tools create one for you.

Change a project name without touching its contents or deployment history.

Hide a project from default listings without deleting it. Reversible with the unarchive action.

Audit your account for duplicates, stale projects, and throwaway test deploys. Recommends, never deletes.

Take a project offline. Soft by default, with a seven-day window in which redeploying the name restores it; hard delete is immediate and permanent.

Point your own domain at a project, or remove the current one. Requires Pro or Team, plus a CNAME record you add at your registrar.

Recent deployments across all projects, or scoped to one.

Everything about one deployment, including the full deployed file contents — the way to recover source a conversation has lost.

Status, status detail, URL, file count, and size for a deployment, or the last five for a project.

Rebuild a project from its stored source. MCP server projects go through the full pipeline again, preserving auth mode and runtime.

Republish an older deployment’s files as a new deployment. Forward-only, so nothing is destroyed.

Permanently remove one deployment record from history.

Turn AI or storage on or off for a running app without redeploying its code. Also where you change the pinned system prompt, widen the model allowlist, or adjust caps. Live within about a minute.

List a project’s stored files. Metadata only, never content. Defaults to the shared scope; pass a user ID for one end user’s files.

Read one file. Text by default, base64 for binary, or metadata only. Files over 256KB come back as metadata rather than inlined.

Write a file (3MB max) where the app and its MCP servers can read it. Publish it at a credential-free URL with public.

Delete a file, and with it any public URL it was served from.

Create an assistant from a model, a system prompt, and connections to MCP servers that already exist. Served from one of your app subdomains via oz.assistant(slug).

Your assistants with their slugs, models, connected servers, and status.

One assistant’s full config and its chat endpoint URL.

Change the model, prompt, connected servers, or limits. Effective immediately, no redeploy.

Delete an assistant. Its chat endpoint stops responding at once.

Talk to one of your assistants server-side — the way to test one before any app exists. Returns the whole reply plus a trace of each tool-use round.

A known-good scaffold to build from: minimal, fetch-api, oauth1-api, storage, files, widget, sync, or python. Start here rather than from scratch.

Build and deploy TypeScript or Python source as a hosted MCP server on a stable endpoint, with your chosen auth mode and an optional cron schedule.

Deployment health, recent deploy records, and a live Cloudflare tail when one is available. The first stop when a server misbehaves.

Which MCP Apps widgets your server exposes and which tools render into each — including tools pointing at a widget that does not exist.

Set an encrypted environment secret, exposed to the server as ctx.env.KEY. Cloudflare picks it up immediately.

The secret keys configured on a server. Values are never returned.

Remove an environment secret.

Replace a token-mode server’s access token. The old one stops working immediately; the new one is shown exactly once.

A federated endpoint at gw.opzero.sh/g/<slug>/mcp. Choose the exposure mode carefully — search is right for Claude.ai.

Your gateways with endpoints and backend counts. Materializes the default gateway on first call.

One gateway in full: exposure policy, backend attachments with namespaces, and per-backend health.

Change the name, exposure mode, inline limit, pinned tools, or tracking flag. Live within about thirty seconds.

Attach a hosted server, an external MCP server, or an assistant, under a namespace that prefixes its tool names. Use an external connection for third-party credentials.

Detach a backend. The backend itself survives; any connection grant it held through this gateway is revoked.

Delete a gateway and its attachments. Backends are untouched. The default gateway cannot be deleted.

Connect Notion, Linear, Sentry, Neon, Vercel, or any RFC 9728 server. Returns a one-time authorize URL; the grant is stored encrypted and refreshed for you.

Your connections with status, granted scope, and which workloads may use each. Status needs_reauth means the grant must be recreated.

Let one workload use one connection, or revoke that permission. This is the consent boundary — nothing is ambient.

Revoke at the provider where supported, delete the stored credential, and drop every grant on it.