Archived: use trilium-mcp-proxy instead
Trilium Notes 0.106+ has its own MCP server at /mcp, so this project is no longer maintained. trilium-mcp-proxy puts an OAuth login in front of it: add one URL to any MCP client and log in once with your Trilium password, with no ETAPI token to create or paste.
Your password never leaves your server: the proxy runs next to Trilium and its login page is its own, so the password goes only from your browser to the proxy and on to your Trilium. It is never stored or logged, and the MCP client never sees it.
trilium-mcp-proxy docs Quick start
Prefer a token? Turn on Trilium's MCP server (Options → AI / LLM → MCP server), create a token under Options → ETAPI and use it as Authorization: Bearer <token>. The rest of this site describes trilium-mcp as it was at its last release.
Your notes in Trilium Notes, as tools for Claude¶
The Trilium Notes MCP server runs next to your Trilium Notes server and turns your AI assistant into a front end for your notes: ask Claude on your phone, desktop or claude.ai, or any other MCP client, to search, write and reorganize them, through every documented ETAPI endpoint.
Once the container is reachable, connecting Claude Code from any machine takes one command, then /mcp to log in with your Trilium Notes password:
claude mcp add trilium --scope user --transport http \
https://trilium-mcp.example.com/mcp
Running more than one Trilium Notes instance? Add one container and one named connection per instance, see Multiple Trilium Notes instances.
What it does¶
- Your assistant becomes the front end. Instead of opening Trilium Notes, you ask: "add this to today's journal", "what did I note about the router?". Claude reads and edits the notes for you, in the desktop and mobile apps or on claude.ai.
- Works from any device. The Trilium Notes MCP server is served over HTTP, so Claude on your laptop, phone or the web can reach it through a reverse proxy, and app clients sign in with OAuth. It runs next to Trilium Notes rather than inside it, so it also works with versions before Trilium Notes' own built-in MCP server.
- Covers the whole ETAPI. All 38 tools (
createNote,getNoteById,searchNotes,exportNoteSubtree, …) are generated at startup from Trilium Notes' OpenAPI spec, so nothing is hand-picked or left out. - Runs as a sidecar. One small container on the same Docker network as Trilium Notes. Only the Trilium Notes MCP server is exposed; Trilium Notes' ETAPI never has to be reachable on its own.
- Two ways to sign in. Log in once in the browser with your Trilium Notes password (OAuth, for remote and app clients), or send an ETAPI token with each request (for scripts and the local network). See Choosing an auth method.
- Stores nothing in token mode. Each client's token is forwarded to Trilium Notes per request, so one sidecar serves many clients.
flowchart LR
app["App client<br>OAuth login"]
headless["Headless client<br>ETAPI token"]
lan["Client on a trusted LAN<br>ETAPI token"]
proxy["Reverse proxy<br>TLS"]
subgraph host["Docker host"]
mcp["trilium-mcp<br>:8081 /mcp"]
oauth[("mcp-oauth<br>encrypted")]
trilium["Trilium<br>:8080 /etapi"]
data[("trilium-data")]
end
app -- HTTPS --> proxy
headless -- HTTPS --> proxy
lan -- HTTP --> mcp
proxy --> mcp
mcp -- OAuth logins --> oauth
mcp -- ETAPI --> trilium
trilium --> data
classDef accent fill:#98D486,stroke:#2f7a27,color:#10200c,stroke-width:1.5px
class mcp accent
Using Claude Code?
Pair this server with trilium-plugin, the client-side counterpart. A skill registers your Trilium instances with Claude Code, and ready-made skills (create, move, rename and search notes, manage attributes, work with templates and journal notes, export a subtree) call these tools for you.