@amenopohis1er/mynotes-mcp
v0.3.0
Published
MCP companion for the My Notes Chrome extension — lets local AI agents search, read, and add to your notes. Local-only: no servers, no network.
Maintainers
Readme
@amenopohis1er/mynotes-mcp
MCP companion for the My Notes Chrome extension — lets local AI agents (Claude Code, or any MCP client) search, read, and add to your notes. Local-only: no servers, no network; every byte stays on your machine, flowing Chrome ↔ this process ↔ your agent. Every line of the published package is inspectable in the Code tab above.
Setup
npx @amenopohis1er/mynotes-mcp install # register the native-messaging host, then restart Chrome- In My Notes → Settings → Labs, turn ON Agent access (MCP).
- Add to your agent's MCP config:
{ "mcpServers": { "mynotes": { "command": "npx", "args": ["-y", "@amenopohis1er/mynotes-mcp"] } } }- Anything wrong?
npx @amenopohis1er/mynotes-mcp doctordiagnoses the whole chain.
Tools
| Tool | What it does |
|---|---|
| search_notes | Full-text search (optionally within a #tag), returns snippets |
| list_notes | Most-recently-updated notes (id, title, pinned) |
| read_note | One note as Markdown (pages via offset for large notes) |
| create_note | New note from Markdown |
| append_to_note | Append Markdown to a note (snapshotted first — restorable from History) |
Chrome must be running with the extension enabled — notes live in the browser's storage and never leave it except through this local bridge. Agent edits are snapshotted to the note's History before they land.
Multiple Chrome profiles? Notes are per-profile, and the bridge serves ONE profile at a time: enable "Agent access" in exactly the profile whose notes your agent should see. If it's on in several, the first to connect wins and the others wait — flip the toggle off in the profiles you don't want exposed.
Questions or issues: https://mynotes.amenophis.dev/contact
