Logseq MCP server

Last verified: 2026-09

Read a Logseq graph.

Community Files & knowledge Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code, VS Code

What it does

Points a model at a Logseq graph over Logseq's HTTP API. Same job as Obsidian: search and edit notes that already live in an outliner, not a random folder.

It sits in Files & knowledge: These servers put the model inside a folder, a notes vault, or a Drive.

Good for

Search a Logseq graph for a page title you only half remember.
Append a block to today's journal from the chat.
Read a page and its blocks without exporting the graph.
Keep the outliner as the system of record instead of copying it into Memory.

Tools

page / block read — Open a page or block.
search — Find pages in the graph.
append / create — Add blocks when the API token allows writes.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "logseq": {
      "command": "npx",
      "args": [
        "-y",
        "logseq-mcp"
      ],
      "env": {
        "LOGSEQ_API_URL": "http://127.0.0.1:12315",
        "LOGSEQ_TOKEN": "from Logseq API settings"
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y logseq-mcp

Secrets it wants: LOGSEQ_API_URL, LOGSEQ_TOKEN

Source repo →

How to get started

Turn on Logseq's API server and copy LOGSEQ_TOKEN.
Set LOGSEQ_API_URL (often http://127.0.0.1:12315) and the token.
Restart the host and ask it to search one page title you know exists.

Access risk

The token is graph-wide. A write-enabled session can append or change daily notes.

When to skip it

Skip it for a plain markdown folder (Filesystem) or an Obsidian vault. Community package — confirm the npm name still matches the repo.

Instead: Obsidian, Filesystem, Memory.

Files & knowledgeObsidianRead and search a local Obsidian vault. OfficialFilesystemRead and write files inside a folder you choose. OfficialMemoryPersistent notes the model can store and recall across chats.

Vs alternatives

Server	Official?	Needs a secret?	Best for
Logseq	No	Yes	Read a Logseq graph.
Obsidian	No	Yes	Read and search a local Obsidian vault.
Filesystem	Yes	No	Read and write files inside a folder you choose.
Memory	Yes	Yes	Persistent notes the model can store and recall across chats.

More in Files & knowledge

OfficialFilesystemRead and write files inside a folder you choose. OfficialGoogle DriveList and read files from a Google Drive account. OfficialMemoryPersistent notes the model can store and recall across chats. Files & knowledgeApple NotesRead local Apple Notes on macOS.

All 6 in this category →

FAQ

What do I turn on in Logseq?

The HTTP API. Set LOGSEQ_API_URL (often http://127.0.0.1:12315) and LOGSEQ_TOKEN from Logseq's settings.

Is the npm package still the same repo?

Community package — confirm the GitHub URL still matches what you install before you put a token in it.

Logseq or Obsidian?

Whichever graph you already live in. Do not run both write tokens on the same notes.

Can it see pages I have not opened?

If the API token can, yes. Treat the token as graph-wide.