Summary
Your Inkdrop notes become searchable and editable in the conversation, and the traffic stays on localhost.
The read path is what makes it worth wiring up: search or list to find candidates, then pull one full body, because listings come back cut to 200 characters. On the write side patch-note is the one to reach for on long notes — an exact string replacement instead of resending the entire body.
What it is
A server for the Inkdrop Local HTTP Server API: the notes, notebooks and tags in your local Inkdrop database, reachable as tools.
What you get
- Keyword search across notes, taking Inkdrop's own qualifiers such as book:, tag:, status: and title:
- The complete body of a note by ID — search and listing return bodies truncated at 200 characters, read-note returns the whole thing
- Backlinks for a note: the notes that link to it, found by searching every body for its link URI
- New notes written straight into a notebook, with status and tags set at creation
- Two ways to edit: update-note replaces only the fields you pass, patch-note swaps one exact string inside a long body
- The notebook list, the tag list, and create and update for tags
Requirements
Inkdrop's local HTTP server switched on, and three environment variables pointing at it: INKDROP_LOCAL_SERVER_URL, INKDROP_LOCAL_USERNAME and INKDROP_LOCAL_PASSWORD. Runs over stdio from npm as @inkdropapp/mcp-server.
Setup effort
One command plus a key — npx -y @inkdropapp/mcp-server, then supply credentials