00Widget
com.00widgetv1.0.0Updated Sep 29, 2026
Publish status cards and Live Activities to iOS widgets, the Lock Screen, and the Dynamic Island.
Installation
In SourceWeft
- Open 00Widget in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"00widget": {
"type": "http",
"url": "https://api.00widget.com/mcp"
}
}
}README
[00Widget — Widgets for all your agents.]
00Widget
Widgets for all your agents.
A reusable Apple-platform companion app and Cloudflare Worker backend that gives Claude, ChatGPT, automations, and software you build a native output channel through widgets, Live Activities, the Dynamic Island, and Apple TV dashboards.
The server never sends UI — only structured state conforming to a small set of templates. The Apple apps render that state through predefined SwiftUI views.
Choose how to connect
Claude, ChatGPT, and other MCP hosts
Hosts that speak the Model Context Protocol can publish to 00Widget with no
integration code: add <BASE_URL>/mcp as a custom connector, sign in, and pick
a tenant. The tools wrap the same handlers as the REST routes, so the two
surfaces cannot drift.
MCP is off by default (MCP_ENABLED in wrangler.toml) because it exposes a
browser flow that mints API tokens on the public internet. Approving a connector
requires signing in, and the credential it issues is a normal tenant token
scoped to the approver's own account, revocable from /admin.
Details: server/README.md → "MCP".
An additive MCP Apps UI can be tested without touching that connector: deploy
the same Worker with MCP_PREVIEW_ENABLED = "true", then add
<BASE_URL>/mcp-preview as a separate Developer Mode connection. It adds
read-only render_card, render_activity, and render_dashboard tools backed
by a versioned HTML resource; /mcp keeps its existing discovery and tool
contract.
Apps, scripts, automations, and coding agents
If you're inside another repo (say, a CI pipeline or a home-automation script) and want to make Claude Code / Codex publish state to your 00Widget instance, paste this into the agent — it's self-contained:
Anatomy
Quick start
1. Backend
Then:
2. Examples
3. iOS
Requires macOS with Xcode 26+, iOS 26 simulator or device, and XcodeGen.
In Xcode, change the bundle id and App Group to values your Apple Developer team owns (see ios/README.md), then run.
Data model
See ios/Sources/Shared/Models/ (Swift) and server/src/types.ts (zod) — the two are kept in lockstep.
- DashboardCard — a single widget tile. Templates:
summary,progress,list,action,chart,history,breakdown,briefing,timeline. - LiveActivitySession — a Lock Screen / Dynamic Island activity.
- ActionDefinition — a button that runs a backend-defined action via
POST /v1/actions/:id/run.
Web sign-in and admin
/login signs a person in with the same Apple ID they use in the iOS app.
Signing in establishes identity, not authority: ADMIN_EMAILS names the
addresses whose sessions additionally carry admin capabilities, and every route
under /admin asserts that capability rather than assuming it.
Signing in does not sign you up. The callback resolves the Apple identity
against the account the app created and turns away one it does not recognise, so
finding this endpoint is not a way to become a tenant. WEB_SIGNUP_ENABLED
(off by default) opts a deployment into web account creation.
The admin dashboard at /admin lists cards, devices, push tokens, Live
Activities, pending activities, and push-to-start tokens across every tenant. It
can also create and revoke tenant credentials and delete tenant data, so access
grants full administrative control rather than read-only visibility. An
API_KEYS bootstrap login (ADMIN_API_TOKEN_LOGIN=true, off by default) covers
a deployment that has no accounts yet.
Create least-privilege tenant API tokens from /admin using the tenant owner email and a permission preset; those generated credentials are what apps and agents use for /v1/*.
Setup walkthrough: server/README.md → "Web sign-in".
Documentation
ios/README.md— Xcode setup, entitlements, signing.server/README.md— Worker deploy, D1 binding, APNs secrets, web sign-in and admin.examples/README.md— publishing state from any shell or agent.docs/llms.md— for agents (Claude Code / Codex) integrating another project with 00Widget.docs/brand/README.md— logo, colors, tagline rules.marketing/screenshots/README.md— raw capture, promotional composition, and App Store screenshot workflow.marketing/app-preview/README.md— App Store Preview capture, rendering, and validation workflow.
Status
Working end-to-end. Cards publish, Live Activities start/update/end, push-to-start is wired, and APNs payloads are verified against Apple's current docs (date-stamped in server/src/apns.ts).
Push-to-start (ActivityKit, iOS 17.2+) — fully implemented. iOS observes Activity<ZeroZeroWidgetActivityAttributes>.pushToStartTokenUpdates from didFinishLaunchingWithOptions, registers via POST /v1/live-activities/register-start-token. The backend's POST /v1/live-activities/start sends the start event to all registered devices and falls back to the pending-queue path if no token is registered (or if the APNs delivery fails). End-to-end verification needs .p8 credentials configured on the Worker.
tvOS activity dashboard — the Apple TV app lists ongoing Live Activities above its widgets. The backend exposes one deduplicated tenant-scoped view across pending starts and registered device activities, while tvOS renders countdowns and progress locally.
WidgetKit pushHandler (iOS 26+) — fully implemented. Each widget configuration calls .pushHandler(ZeroZeroWidgetPushHandler.self). The handler persists WidgetKit’s canonical token/configuration snapshot in the App Group, and the host app reconciles it at launch, on foreground, after app-build changes, and through a short bounded retry while WidgetKit finishes generating a token. Backend pushes carry aps.content-changed: true, use budget-aware per-tenant cadence, and durably coalesce suppressed changes into one delayed queue delivery when the cadence window opens. A successful foreground app fetch also requests targeted timeline reloads immediately. End-to-end verification still needs .p8 credentials and a physical device.
License
Source code is MIT licensed. The 00Widget name and brand assets are excluded; see LICENSE and docs/brand/LICENSE.
Source: README.md at commit 7b7ec1e
Tools
0Version history
1- v1.0.0LatestSep 16, 2026

