Host integration path, not front-door positioning

Use this starter pack when you want the shortest honest path from OpenClaw to Apple Notes Snapshot through MCP.

This is a repo-owned OpenClaw starter pack, not an OpenClaw marketplace artifact and not a claim that Apple Notes Snapshot should be positioned as a front-door assistant. It packages the current MCP registry starting point, the proof boundary, and the repo-owned post-attach checks in one place.

Best fit

  • You already use OpenClaw and want it to inspect Apple Notes Snapshot through the read-only MCP surface.
  • You want a copyable MCP registry starting point instead of translating the Integration Pack by hand.
  • You want a repo-owned explanation of what is proven here versus what still belongs to your OpenClaw host.

Proof level today

  • Repo-side proof: the generic stdio MCP server, tools, resources, help contract, and OpenClaw registry examples are shipped in this repository.
  • OpenClaw proof: the MCP registry path is documented and copyable, and a fresh profile-isolated attach proof now exists on the current host build.
  • Fresh config + attach proof: the official OpenClaw CLI now has a fresh profile-isolated config proof on the current machine, including mcp set, mcp list --json, and mcp show --json for the Apple Notes Snapshot entry, followed by a local agent turn that called the repo MCP tools successfully.
  • Still host-side verify on another machine: your OpenClaw install, provider wiring, MCP registry behavior, and attach result can still differ outside the current verified host.

Install path

  1. Install or update OpenClaw with the current official docs.
  2. Confirm this repository already has a healthy local snapshot loop.
  3. Use the repo-owned MCP registration command or payload below as your starting point.
openclaw mcp set apple-notes-snapshot '{"command":"/absolute/path/to/notesctl","args":["mcp"]}'

Need the tracked files? Use openclaw-mcp-set.txt or openclaw-mcp.json.

Registry and attach path

  1. Register the MCP server with the command above or by loading the JSON payload into the current OpenClaw MCP registry surface.
  2. Point the command at the real /absolute/path/to/notesctl for this checkout.
  3. Let OpenClaw launch the stdio server through notesctl mcp.

Verify path

  1. Confirm the host sees the current v1 tools and resources.
  2. Compare host-visible get_status output against local ./notesctl status --json.
  3. If OpenClaw attaches but shows a missing-state view, initialize the snapshot loop before treating that as an MCP failure.

Use the tracked post-attach checklist for the repo-owned verification steps.

What this starter pack includes

Official public surface truth

  • What exists: OpenClaw documents ClawHub as a real public registry and discovery route.
  • What this repo ships now: MCP registry payloads plus a bundle-compatible local plugin pack that follows the documented Claude/Codex-style bundle layouts OpenClaw can read, and the official OpenClaw CLI has now written, read back, and locally attached to the MCP config on the current machine.
  • What still stays outside this round: a live ClawHub listing or a repo-owned guarantee that every OpenClaw build already attaches the same way.

What it does not claim

  • No OpenClaw marketplace listing
  • No hosted MCP or remote control plane
  • No repo-owned proof that every OpenClaw release or every machine will attach the same way
  • No front-door assistant positioning for Apple Notes Snapshot
  • No public SDK or OpenAPI surface

Release and update story

  • Repo-owned examples and docs move with Apple Notes Snapshot releases and current-main updates.
  • OpenClaw config locations, MCP registry behavior, and host menus can change faster than this repo does.
  • Use release history for the repo-owned side and the official OpenClaw docs for the current host-side steps.

Official docs to pair with this starter pack