MCP support was one of the most common requests I received. The obvious implementation was to expose basic CRUD operations, but I didn’t want an AI client to silently overwrite or permanently delete someone’s notes.
So I limited it to eight tools for searching, reading, opening, creating, appending, updating, trashing, and restoring notes. Access is split into Read, Write, and Trash permissions, and disabled tools disappear from the client entirely.
The MCP server and note storage run locally. Anything a client reads may still be sent to its chosen model provider, of course.
I’m curious whether this feels like the right boundary. Would you want more granular, per-note permissions, or would that make the setup unnecessarily complicated?
Noticky requires macOS 15+ and costs $6.99 once, with no subscription.
Hi I’m Leonidas, the developer behind Noticky.
MCP support was one of the most common requests I received. The obvious implementation was to expose basic CRUD operations, but I didn’t want an AI client to silently overwrite or permanently delete someone’s notes.
So I limited it to eight tools for searching, reading, opening, creating, appending, updating, trashing, and restoring notes. Access is split into Read, Write, and Trash permissions, and disabled tools disappear from the client entirely.
The MCP server and note storage run locally. Anything a client reads may still be sent to its chosen model provider, of course.
I’m curious whether this feels like the right boundary. Would you want more granular, per-note permissions, or would that make the setup unnecessarily complicated?
Noticky requires macOS 15+ and costs $6.99 once, with no subscription.