Semantic search is the reason to connect this rather than open the app: "what have I saved on Postgres indexing" finds the right save without you remembering the title. Captures enrich asynchronously, so a fresh link comes back `pending` and is worth re-reading once it says `ready`.
A local stdio MCP server for Memlane, a personal library of saved links and notes. Your host spawns it with `npx` and it talks to the Memlane API with your key; every tool returns pretty-printed JSON in a single text block, with no streaming.
- search_saves — semantic search across embedded link and note content, each match scored 0–1
- list_saves — browse newest first with cursor pagination and filters for project, topic name, kind, status and a title substring
- get_save — one save's metadata, or the full markdown body with `includeContent: true`
- capture_url — save a link; extraction, summary, embedding and topic classification run in the background, so it returns `pending` and becomes `ready` later
- create_note / update_note — write and edit markdown notes, embedded immediately so they are searchable straight away
- list_projects / list_topics — resolve project and topic names to ids
- add_topic_to_save / remove_topic_from_save — tag and untag
- Deleting a save is not exposed as a tool; that stays on the REST API
A Memlane account and an API key from Manage → Connections → API keys, passed as `MEMLANE_API_KEY`; `MEMLANE_API_URL` is optional and defaults to https://api.memlane.io. Node 18+ for `npx`. Keys carry read, write and capture scopes, and a call outside its scope fails with `insufficient scope`. ChatGPT, Claude Desktop and other remote clients cannot run `npx` — they use the hosted endpoint at https://api.memlane.io/mcp over OAuth, with no API key at all.
One command plus a key — npx -y @memlane/mcp, then supply credentials