00Widget

com.00widget由 00widget.com 發布官方發布者v1.0.0更新於 Oct 24, 2026

Publish status cards and Live Activities to iOS widgets, the Lock Screen, and the Dynamic Island.

已驗證Streamable HTTP可網頁執行效率與工作流開發者工具

概覽

AI 產生的概覽

遠端 MCP 伺服器,讓助理把狀態卡片和即時活動發佈到 iOS 小工具、鎖定畫面、動態島和 Apple TV 儀表板。

可以做什麼
  • 使用 summary、progress、list、action、chart、history、breakdown、briefing、timeline 等範本發佈儀表板卡片,作為小工具磚
  • 在鎖定畫面和動態島上啟動、更新和結束即時活動
  • 透過卡片上的動作按鈕執行後端定義的動作
  • 透過選用的預覽工具以唯讀方式呈現卡片、活動和儀表板
  • 透過網頁管理後台管理租戶、裝置、推送權杖和憑證
適用情境
適合希望讓代理、指令碼或 CI 流程把狀態、建置進度、佇列深度或有限時的進度以原生方式顯示在 Apple 裝置上,而不是只留在聊天視窗中的情境。
執行需求
需要一個遠端端點並新增為自訂連接器,透過 OAuth 登入並選擇租戶;部署端必須啟用 MCP,因為此功能預設關閉。自架後端執行於 Cloudflare Worker,需要 D1 繫結、APNs 憑證和工作階段密鑰。
安裝前請注意
核准連接器會簽發一個限定在核准者帳號下的租戶 API 權杖,可從管理頁面撤銷。管理後台可以建立和撤銷憑證,並刪除租戶資料。卡片欄位會顯示在鎖定畫面上,因此不應發佈密鑰或個人資料;不應讓破壞性動作從小工具自動執行。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 00Widget,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.00widget%2F00widget/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "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:

Integrate this project with 00Widget so its state shows up on iOS widgets and Live Activities.
Read the integration contract: https://github.com/morais/00widget/blob/main/docs/llms.mdThat single document is everything you need — don't pull in the rest of the 00Widget repo.
Operator-supplied env vars:  00WIDGET_BASE_URL=https://api.example.com  00WIDGET_API_KEY=<bearer token>
Verify both work with `curl $00WIDGET_BASE_URL/health` and an authenticated `GET /v1/cards` before writing any code.
Then:1. Identify the surfaces in this project that an iOS widget should reflect (status, build state, queue depth, in-progress jobs, etc.).2. For each, pick a template (`summary`, `progress`, `list`, `action`, `chart`, `history`, `breakdown`, `briefing`, or `timeline`) per llms.md's decision matrix.3. Add the smallest possible publish path — POST one card to `/v1/cards/upsert`, or one related snapshot to `/v1/cards/upsert-batch`, using stable ids. No SDK, no class hierarchy.4. If something is time-bounded with a clear end (a build, a charge cycle, a delivery), use a Live Activity instead of a card.
Constraints:- Use a stable `id` per logical thing — never embed timestamps or run ids.- Never put secrets or PII in card fields. They render on the Lock Screen.- Always end Live Activities. Never make destructive actions auto-run from widgets.- Don't publish more than ~once a minute per card unless the value actually changed.
If this project is itself a Cloudflare Worker, see the "Notes for Cloudflare Workers callers" section in llms.md — same-account integrations should use a Service Binding instead of a public HTTPS fetch.

Anatomy

00widget/  ios/          # SwiftUI app + WidgetKit extension + Live Activity (iOS 26+)  server/       # Cloudflare Worker (TypeScript) — REST API + APNs fan-out  examples/     # curl scripts showing how any agent can publish state  marketing/    # Screenshot and App Preview sources, docs, and entry points  artifacts/    # Generated marketing output (ignored by Git)

Quick start

1. Backend

cd servernpm installinstall -m 600 .dev.vars.example .dev.vars   # fill in SESSION_SECRET; enable the local fallback only when needednpx wrangler dev

Then:

curl -s http://localhost:8787/health

2. Examples

cd examplesinstall -m 600 env.example.sh env.sh   # edit BASE_URL and API_KEY./upsert-solar.sh

3. iOS

Requires macOS with Xcode 26+, iOS 26 simulator or device, and XcodeGen.

brew install xcodegencd iosxcodegenopen ZeroZeroWidget.xcodeproj

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.

Administration is enabled by default. Set ADMIN_ENABLED = "false" under [vars] in server/wrangler.toml and redeploy to make /admin and all its mutation endpoints return 404 before session or database access. Web sign-in, the account dashboard, MCP authorization, and the public API remain available.

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.

來源:README.md,提交 f98ddff

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。