Use this starter pack when you want the shortest honest path from Apple Notes Snapshot to a Claude Code MCP setup.
This is a repo-owned Claude Code starter pack, not an official Claude Code plugin. It packages the current project-scoped and user-scoped MCP examples, the repo-owned post-attach checks, and the proof boundary between this repository and your Claude host.
Best fit
- You want Apple Notes Snapshot available through Claude Code on the same machine.
- You need to choose between project-scoped and user-scoped registration.
- You want a repo-owned explanation of what is proven here versus what still belongs to the Claude host.
Proof level today
- Repo-side proof: the generic stdio MCP server, tools, resources, and help contract are shipped and tested in this repository.
- Claude Code proof: project and user MCP example files are tracked and current.
- Fresh attach proof: this repository now has a fresh Claude Code attach proof on the current host build.
- Still host-side verify on another machine: your own Claude Code install, login state, permission prompts, and live attach result can still vary outside this proofed host session.
Install path
- Install or update Claude Code with the current official host docs.
- Confirm this repository already has a healthy local snapshot loop.
- Choose whether you want project-scoped or user-scoped MCP registration.
Config path
- Project-scoped surfaces: use the tracked
.mcp.json-style example and the repo-level instruction surfaces Claude Code recognizes, such asCLAUDE.mdor project settings. - User-scoped surface: use the user MCP example when you want one local machine registration reused across repositories.
- Local private override: keep machine-specific secrets or overrides outside tracked files.
Register and attach path
Use one of the tracked example files below as your starting point, then point the server
command at the real /absolute/path/to/notesctl for this checkout.
Verify path
- Confirm the host sees the current v1 tools and resources.
- Compare host-visible
get_statusoutput against local./notesctl status --json. - If the host attaches but shows missing-state output, initialize the snapshot loop before you call it an MCP failure.
Use the tracked post-attach checklist for the repo-owned verification steps.
What this starter pack includes
- Repo-owned Claude Code local marketplace
- Control-room plugin bundle
- Project-scoped MCP example
- User-scoped MCP example
- Generic stdio MCP launch shape
- Repo-owned post-attach checklist
- Public skills pack for public-safe prompt and contract guardrails
Official public surface truth
- What exists: Claude Code has an official plugin marketplace surface and an official marketplace repository.
- What this repo claims: the local marketplace bundle and plugin files are repo-owned and installable as a local distribution surface, and a fresh attach proof now exists on the current host build.
- What this repo still does not claim: Anthropic has officially listed Apple Notes Snapshot in its marketplace, or that every Claude Code host build already proves attach.
Recommended companion guidance
- Use the public skills pack if you want repo-scoped wording and builder-contract guardrails alongside the Claude setup itself.
- Start with runtime-resource-hygiene when your Claude Code workflow also needs explicit browser/profile cleanup and branch/worktree/PR convergence rules after the task ends.
- Keep the boundary honest: these guidance files improve team discipline, but they do not make this repo an official Claude Code plugin or marketplace artifact.
What it does not claim
- No official Claude Code marketplace listing
- No repo-owned proof that every Claude Code release will attach the same way
- No hosted MCP or public API promise
- No public SDK or plugin marketplace story
Release and update story
- Repo-owned examples and docs move with Apple Notes Snapshot releases and current-main updates.
- Refresh the local marketplace with
claude plugin marketplace update apple-notes-snapshot-localafter you pull new repo changes. - Claude Code host menus, permission prompts, and config locations can change faster than this repo does.
- Use release history for the repo-owned side and the official Claude docs for the current host-side steps.