Skip to content

Claude Code

Register the Trilium Notes MCP server with claude mcp add. Pick the auth method per connection.

OAuth

Register the URL with no header. The client opens the login page on first use:

claude mcp add trilium --scope user --transport http \
  https://trilium-mcp.example.com/mcp

In Claude Code, run /mcp and pick the server to authenticate.

Each client gets its own ETAPI token, visible and deletable under Options → ETAPI in Trilium Notes. Deleting it there, or revoking the OAuth token, disconnects just that client.

ETAPI token

The ETAPI token is the credential: pass it in the Authorization header. Point the URL at wherever the Trilium Notes MCP server is reachable.

claude mcp add trilium --scope user --transport http \
  https://trilium-mcp.example.com/mcp \
  --header "Authorization: YOUR_TRILIUM_ETAPI_TOKEN"
claude mcp add trilium --scope user --transport http \
  http://192.168.1.50:8081/mcp \
  --header "Authorization: YOUR_TRILIUM_ETAPI_TOKEN"

Commit a project-level config instead, filling in your host and token (a copy is in the repo as .mcp.json):

{
  "mcpServers": {
    "trilium": {
      "type": "http",
      "url": "https://trilium-mcp.example.com/mcp",
      "headers": {
        "Authorization": "YOUR_TRILIUM_ETAPI_TOKEN"
      }
    }
  }
}

The raw token is what Trilium's ETAPI expects. A Bearer prefix is also accepted and stripped before the request is forwarded, so Authorization: Bearer YOUR_TOKEN works too.

Multiple Trilium instances

Add one connection per trilium-mcp container under its own name, such as trilium-home and trilium-work. See Multiple Trilium instances.

User or project scope

--scope user registers the server across all your projects, which is usually what you want for a personal knowledge base. Drop it to fall back to the default local scope, available only to you in the current project. This works the same with either auth method:

claude mcp add trilium --transport http \
  https://trilium-mcp.example.com/mcp