TriliumNext (Trilium Mcp)
Connect Claude Code, Cursor, or Codex to a self-hosted TriliumNext wiki so agents can search, read, and update your notes without leaving the terminal.
Overview
TriliumNext (trilium-mcp) is a MCP server for the Build phase that reads and writes a self-hosted TriliumNext knowledge base over ETAPI so coding agents can use your notes as live context.
What is this MCP server?
- Read and write TriliumNext notes via the official ETAPI with a bearer token from Options → ETAPI
- Stdio MCP transport packaged as OCI image ghcr.io/ovden13/trilium-mcp:0.1.5 for Claude Desktop and compatible hosts
- Comma-separated TRILIUM_URL failover (LAN first, public HTTPS fallback) for home-lab and remote setups
- Configurable TRILIUM_HTTP_TIMEOUT_SECONDS (default 30) and TRILIUM_MCP_LOG (off / info / debug) on stderr
- Self-hosted only: requires your own TriliumNext instance—no cloud SaaS substitute in the server
- Server version 0.1.5 per MCP registry schema
- OCI identifier ghcr.io/ovden13/trilium-mcp:0.1.5 with stdio transport
- Required env: TRILIUM_URL and TRILIUM_TOKEN; default HTTP timeout 30 seconds
Community signal: 1 GitHub stars.
What problem does it solve?
Agents cannot see your Trilium wiki unless you manually export or paste notes, which breaks flow and stale context during solo shipping.
Who is it for?
Solo builders who self-host TriliumNext and want Claude Code or Cursor to pull specs, tasks, and research from the same ETAPI token they already use for automation.
Skip if: Teams that do not run Trilium, want a hosted notes SaaS with no server, or need full-text search UX and graph editing only inside Trilium’s web app without agent tools.
What do I get? / Deliverables
After you configure TRILIUM_URL and TRILIUM_TOKEN in your MCP host, agents can query and update Trilium notes in-tool while you code or plan.
- Agent-callable tools to read and write notes in your Trilium knowledge base
- Configurable ETAPI connection with optional multi-URL failover and request timeouts
- Versioned OCI-deployable MCP server (0.1.5) for repeatable local or container setups
Recommended MCP Servers
Journey fit
The canonical shelf is Build because solo builders typically wire this MCP while assembling their agent stack and linking local knowledge to coding workflows, even though notes remain useful later in Operate. Integrations fits an ETAPI-backed bridge that exposes Trilium as tools over stdio rather than a standalone note app or a ship-time security check.
How it compares
MCP integration over Trilium ETAPI, not an agent skill or a replacement Trilium desktop client.
Common Questions / FAQ
Who is TriliumNext (Trilium Mcp) for?
It is for solo and indie builders who already use self-hosted TriliumNext and want their AI coding agent to read and write notes through the official ETAPI.
When should I use TriliumNext (Trilium Mcp)?
Use it when you are wiring your agent stack in Build and need durable wiki context—specs, checklists, research—available during implementation without manual copy-paste.
How do I add TriliumNext (Trilium Mcp) to my agent?
Run the OCI package over stdio in your MCP client, set TRILIUM_URL to your instance base URL (comma-separated for failover), create an ETAPI token in Trilium under Options → ETAPI, and set TRILIUM_TOKEN as a secret.