Project-scoped, not marketplace-scoped

Use this starter pack when you want the shortest honest path from Apple Notes Snapshot to a Codex MCP setup.

This is a repo-owned Codex starter pack, not an official Codex plugin. It packages the current generic stdio MCP path, the trusted-project reminder, and the repo-owned post-attach checks in one place.

Best fit

  • You already use Codex and want Apple Notes Snapshot to expose local backup facts through MCP.
  • You want a project-scoped setup story instead of a global hosted service story.
  • You want a repo-owned checklist that tells you what is proven here versus what still belongs to your Codex host.

Proof level today

  • Repo-side proof: the generic stdio MCP server, tools, resources, and help contract are shipped and tested in this repository.
  • Codex proof: the registration path is documented and copyable, and a fresh named-host attach proof now exists on the current host build.
  • Still host-side verify on another machine: your Codex install, trusted-project status, and any host-specific attach differences outside the current verified host.

Treat this pack like a verified wiring kit on the current host build: the connector shape is real and the current machine now has a fresh attach proof, but another Codex install can still differ and should be rechecked locally.

Install path

  1. Install or update Codex with the current official host docs.
  2. Confirm this repository has a healthy local snapshot loop before you attach anything.
  3. Use the repo-owned add command below to register the MCP server.
codex mcp add apple-notes-snapshot -- /absolute/path/to/notesctl mcp

Need the tracked text file? Use codex-mcp-add.txt.

Config path and trust boundary

  • Codex host config: Codex keeps its own user-level and project-level config surfaces.
  • Project-scoped reminder: if your Codex build uses trusted-project gates, the project-level config only matters after the repo is trusted on that machine.
  • Repo-owned boundary: this repository does not try to hide or bypass that trust step.

Attach path

  1. Register the MCP server with the add command above.
  2. Open or work inside this repository on the same machine where /absolute/path/to/notesctl exists.
  3. Let Codex launch the stdio server through notesctl mcp.

The narrow repo-owned claim is the launch shape, not a promise that every Codex release or UI flow looks identical.

Verify path

  1. Confirm the host sees the current v1 tools: get_status, run_doctor, verify_freshness, get_log_health, list_recent_runs, and get_access_policy.
  2. Confirm the host can read the current v1 resources: notes-snapshot://state.json, notes-snapshot://summary.txt, notes-snapshot://recent-runs, and notes-snapshot://config-safe-summary.
  3. Run ./notesctl status --json locally and compare it with the host-visible status response.

Use the tracked post-attach checklist if you want the same steps in Markdown form.

What this starter pack includes

Official public surface truth

  • What exists: OpenAI now documents Codex plugins and an official plugin directory.
  • What is still blocked: the same official docs still say public third-party plugins in the official directory are coming soon.
  • What this repo ships now: a local marketplace file and a plugin-grade bundle you can keep alongside the project without pretending it is already in OpenAI's official directory.

Recommended companion guidance

  • Use the public skills pack if you want repo-scoped wording and builder-contract guardrails in the same place as your Codex setup.
  • Start with runtime-resource-hygiene when your Codex workflow also needs explicit browser/profile cleanup and branch/worktree/PR convergence rules after the task ends.
  • Keep the boundary honest: these guidance files help the team operate cleanly, but they do not turn this repo into an official Codex plugin or marketplace package.

What it does not claim

  • No official Codex marketplace listing
  • No hosted MCP or remote control plane
  • No promise that this repository has already verified attach on every Codex release or every machine
  • No public SDK or OpenAPI surface

Release and update story

  • Repo-owned example files and docs will move with Apple Notes Snapshot releases and current-main updates.
  • Refresh the local bundle by pulling the repo, then rereading the bundle README and marketplace file before you call a plugin install current.
  • Codex host menus, trust prompts, and extra MCP options can change faster than this repo does.
  • Use release history for the repo-owned side and the official Codex docs for the current host-side steps.

Official docs to pair with this starter pack