For agents
The memory layer your agents need
Ela exposes your notes through MCP, the protocol agents already speak. Search returns structured handles with provenance, not raw file dumps. Coverage metadata on every response.
MCP exposes read tools only. Agent writes go through the HTTP API, CLI --remote, or the web review queue.
Local vs cloud
Two endpoints, one retrieval model
Local runs on your machine with full folder access, including private/. Cloud serves AI running anywhere, scoped to your vault and nothing else.
Desktop search is lexical-only. Semantic search is opt-in on local MCP and hybrid on cloud when hosted.
Ranked search
Lexical ranking always. Semantic is opt-in on local (ELANOTES_EMBEDDINGS=1, one-time model download) and hybrid on cloud.
Citations on every result
The note, the heading, the dates. Answers with receipts.
Coverage reporting
Know what was searched and what was excluded
private/ folder access
Sensitive notes are served from your machine only
Offline operation
Works without internet, entirely on your hardware
Remote agent access
An endpoint for AI running anywhere
MCP tools
Everything an agent needs to know you
A complete read surface: search, browse, follow connections, catch up on changes. Every response comes with citations and coverage.
MCP tools are read-only. Agents write through the HTTP API, CLI --remote, or the web review queue.
search_notesRanked search that returns citations, not walls of text.
grep_notesExact-match search that always works, even on a note saved a second ago.
read_noteFetch a note, or just the lines needed. Never a context-window blowout.
list_notesBrowse folders so an agent can see what is in the vault.
get_linksFollow backlinks, tags, and related notes.
recent_changesCatch up on what changed since the agent last looked.
index_statusCheck how fresh the index is before trusting it.
vault_infoWhat this vault contains, and what the caller is allowed to see.
Setup
Connect in minutes
Build the package from a clone first. The server is not published to npm.
Run the local MCP server
pnpm --filter @elanotes/mcp-local build
{
"mcpServers": {
"elanotes": {
"command": "node",
"args": [
"/ABS/PATH/TO/elanotes/packages/mcp-local/dist/cli.js",
"--vault",
"/ABS/PATH/TO/your/vault"
]
}
}
}VAULT_PATH is the env equivalent of --vault.
Cloud MCP is not live
Local MCP is the supported setup today. A hosted cloud MCP endpoint is not available yet.
Design principles
Built for agents that need to trust results
These hold at every layer. They are what make Ela memory instead of just search.
These invariants apply to every retrieval path, local or cloud.
Citations, not dumps
Search returns pointers with provenance. Agents fetch only what they need. Less token waste, less room to hallucinate.
Coverage on every response
Every answer says what was searched, what was excluded, and why. Silent gaps are the worst failure mode. Ela does not have them.
Same question, same answer
Results are reproducible, not a slot machine. An agent that asks twice gets the same truth twice.
Your vault is yours alone
Strict isolation between vaults, verified continuously. Never an afterthought.
Zero is a valid answer
Ela returns nothing, with an explanation, rather than padding results with noise. Agents learn when to say "I don't know."
private/ never leaks
Your local setup sees your private/ folder. The cloud never does, not in results, logs, or caches. Enforced and tested on every release.
Point it at a folder. Start asking.
Keep the notes you have. Connect the tools you already use. Local is free.
Local tier, MCP server, and the web and desktop apps work today. Cloud hosting and the desktop signing pipeline are not live yet.