OpZero Capability Atlas
One MCP endpoint in, production infrastructure out. This page maps the full capability ecosystem and was itself produced by it: deployed over raw MCP from a live Claude chat, with data flowing through the federated gateway the whole way.
Census 2026-08-10 · 16 backends · 82 federated tools · 46 bridge tools
The loop that built this page
Claude chat → POST https://opzero.sh/mcp (streamable HTTP, bearer auth) → deploy_themed / deploy_markdown → production hosting, while live readings arrived via Claude chat → gw.opzero.sh → invoke_tool → 16 federated backends. Every layer of the platform participated in its own documentation.
Platform layers
1 · Deploy bridge
Instant production deploys from agent conversation: deploy_html, deploy_files, deploy_react_artifact, deploy_themed, deploy_markdown. Tailwind compiled server side, theme CSS injected, three hosting targets behind one verb.
2 · Lifecycle
Deploys are records, not fire and forget: redeploy, rollback_deployment, update_deployment (incremental merges), project_cleanup with staleness analysis, full deploy history with file contents.
3 · Runtime bindings
configure_bindings attaches AI inference, durable storage, and SDK injection to an already deployed app without touching its code. Static pages graduate into stateful apps.
4 · Hosted MCP servers
Deployed servers become tools. Three archetypes proven in production: Overseer (per user KV state), Intel (external API fetch with caching), Holocron (MCP Apps widget with a state machine).
5 · Gateway federation
gw.opzero.sh fronts every deployed server behind one endpoint. track_all_deployed auto federates new deploys; search_tools discovers live at call time; invoke_tool routes with auth handled per backend.
6 · Assistants & connections
deploy_assistant turns a model, prompt, and MCP connections into a chat endpoint other workloads can call. grant_connection scopes external MCP credentials per workload: consent as an API.
Federated mesh census
| Namespace | Tools | Archetype | What it proves |
|---|---|---|---|
garmin | 10 | Intel + Overseer | Synced external store with write ingest |
fragments | 9 | Overseer | Per user KV, full CRUD, widget rendering |
shelf | 8 | Overseer | Profile driven agent instructions |
scriptorium | 8 | Overseer | GitHub backed manuscript workflows |
krakens_locker | 6 | Compute | Deterministic generation |
battlestation_overseer | 6 | Overseer | KV ledger + shared broadcast |
bridge_probe | 5 | Holocron | Host bridge compatibility probing |
battlestation_holocron | 4 | Holocron | Widget state machine |
hooch_gauge | 3 | Intel | Live USGS fetch, sparkline widget |
battlestation_intel | 3 | Intel | GitHub + weather sensors |
jefe_toolkit | 3 | Compute | Crypto primitives at the edge |
forge_mcp | 3 | Compute | Pure deterministic functions |
oz_widget_demo | 3 | Holocron | Durable counter widget |
loop_mcp | 2 | AI relay | Edge inference (degraded, see manifest) |
chatgpt_mcp_smoke_test | 2 | Diagnostic | Cross host compatibility |
gw_route_check_0719 | 2 | Diagnostic | Routing + identity proof |
Live proof of interconnectivity
Identity survives federation
The routing check answered polo and named the caller: the backend saw jeff@opzero.io through two worker hops.
The river is in the mesh
Roswell running 2050 cfs at 4.08 ft. Real USGS data fetched by a deployed server, routed through the gateway, baked into this deploy.
State persists across weeks
A fleetwide directive written to KV on July 20 read back intact on August 10: durable per user state behind the federation.
Three deploys, one MCP session, from the QA account. The multi provider attempt surfaced defect OZ-DEPLOY-002, documented in the manifest; the suite serves from the Cloudflare target.