Obsidian is the highest-value and highest-risk entry in this list. High value because a vault is the richest personal context a model can get. High risk because notes are plain files and a careless write is a silent loss, with no trash and no undo unless your vault is in version control.
The two architectures, and why it matters
Some servers read and write vault files directly on disk. Others talk to Obsidian through the Local REST API plugin. Direct file access works whether Obsidian is open or not and is faster. The plugin route respects what Obsidian knows about links and metadata, but needs the app running. Pick file access for batch reading; pick the plugin when link and metadata fidelity matters.
Protect the vault before you connect it
Put the vault in Git, or at minimum turn on a versioned backup, before granting any write access. Then start read-only. Most of what makes this worth doing — "find every note where I wrote about this client", "summarise this month's meeting notes" — needs no write access at all.
The context ceiling nobody mentions
A vault of a few thousand notes does not fit in any assistant's context. What you get back is an answer based on whatever the search surfaced, presented with full confidence. For anything that matters, ask which notes it used.
Where LemTask stands today
LemTask does not ship an MCP server yet, and we are not going to pretend otherwise on a page developers will read. What LemTask has working right now is outbound and inbound webhooks, Zapier, Make and Apple Shortcuts, which covers "when a task is created, do X" and "create a task from anything that can send an HTTP request". An MCP connection is on the roadmap; when it ships and we have tested it end to end with Claude, this page will say so with the config block, and not a day earlier.