Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
A read-only MCP server that lets Claude (or any MCP client) search and read your LogSeq graph. It follows links, builds context for a topic and reads journals by date, using batched Datalog queries so a question costs a handful of LogSeq calls, not one per page.
Read-only MCP server that lets Claude search and read your LogSeq graph: page context, link traversal and journals by date. Batched Datalog keeps a question to a handful of calls. Native Rust binary, plus Claude Code plugin skills.
It never writes to your graph. Every tool only reads.
Install: see Install (Claude Code plugin, uvx, or a clone).
You keep notes in LogSeq and want an AI assistant to use them: "what do I know about project atlas?", "what was I working on last week?", "how does this page connect to that one?". You run LogSeq desktop with its HTTP API on, reachable at apiUrl (default 127.0.0.1).
10 tools in four kinds, named after what they do:
Long results are cut with a warning and a nextCursor you pass back as cursor. Details, parameters, Markdown output, prompts and resources: docs/tools.md.
You need LogSeq desktop with its HTTP API on, and one of the options below. The server is a native Rust binary; Node is only for developing it.
1. Set up LogSeq. Turn on the HTTP API server (Settings, then API) and generate an auth token. Then create ~/.logseq-mcp/config.json:
{
"apiUrl": "http://127.0.0.1:12315",
"authToken": "your-token-here"
}
The token lives only in that file, so no credentials go in your client's config. Other settings and environment variables: docs/configuration.md.
2. Connect a client. Pick one.
Claude Code plugin (also bundles the skills, and downloads the release binary for you):
claude plugin marketplace add eborden/logseq-mcp-server
claude plugin install logseq@logseq-mcp-server
Claude Code with uvx (needs uv; the package is logseq-mcp-server on PyPI):
claude mcp add logseq -- uvx logseq-mcp-server
Claude Desktop, in claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json), then restart it:
{
"mcpServers": {
"logseq": {
"command": "uvx",
"args": ["logseq-mcp-server"]
}
}
}
From a clone (needed on Windows and Linux arm64, which have no prebuilt binary or wheel): build with cargo build --release --locked (see docs/development.md), then use the absolute path of target/release/logseq-mcp-server as the command, with no args.
Prebuilt binaries and wheels cover macOS (Apple silicon and Intel) and Linux x86_64. A desktop app may not find uvx on its PATH; if so, set command to the full path of uvx. There is no npm package: the name logseq-mcp-server on npm is not this project, so don't run npx logseq-mcp-server. Plugin details (cache, checksums, offline use): docs/plugin.md.
The logseq-skills workflows (recall a topic, refresh on a person, history of a decision, connect two projects, plan the week, stale work, who owns it, weekly and monthly summaries, link concepts) ship with the plugin and live in skills/logseq-skills/. The server also offers five prompts and two resources; see docs/tools.md.
apiUrl, 127.0.0.1 by default). It makes no other network calls while serving, and it logs to stderr only, never graph content.~/.logseq-mcp/config.json. Error messages never echo it.Licensed under MIT; see LICENSE.
Read-only MCP server that lets Claude search and read your LogSeq graph: page context, link traversal and journals by date. Batched Datalog keeps a question to a handful of calls. Native Rust binary,
Übersicht
Read-only MCP server that lets Claude search and read your LogSeq graph: page context, link traversal and journals by date. Batched Datalog keeps a question to a handful of calls. Native Rust binary, plus Claude Code plugin skills.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Logseq läuft lokal über stdio.
Zuletzt geprüft: 2026-10-28. Read-only MCP server that lets Claude search and read your LogSeq graph: page context, link traversal and journals by date. Batched Datalog keeps a question to a handful of calls. Native Rust binary, plus Claude Code plugin skills.
