LogSeq MCP server
Commit Oct 28, 2026Allows an AI client to search and read your LogSeq graph, including page context, link traversal, and journal entries by date.
Also known as eborden/logseq-mcp-server
- Stars
- 2
- Tools
- 4
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 28, 2026
- License
- MIT
What is LogSeq MCP?
LogSeq allows an AI client to search and read your LogSeq graph, including page context, link traversal, and journal entries by date. It exposes 4 tools, such as get, find, explore.
Summary generated from the project's README
About LogSeq MCP server
Accessing your personal knowledge base through an AI assistant is possible with this read-only server. It allows Claude or other MCP clients to search and interpret your LogSeq graph by following links, traversing page context, and reading journal entries by specific dates. Because it uses batched Datalog queries, the server can answer complex questions about your notes without making a separate call for every single page.
To use this, you must have LogSeq desktop running with the HTTP API enabled. You will need to provide an API URL and an authentication token within a local configuration file. The server connects to your local instance, typically at 127.0.0.1, and never writes to or modifies your data. It provides ten distinct tools categorized into get, find, explore, and check functions to help you retrieve specific blocks, find pages matching filters, or explore the network of links within your graph.
Developers can set this up using the Claude Code plugin, uvx, or by building the Rust binary from a clone. It is designed for users who want to ask questions about project history, find connections between different topics, or summarize their work over specific time periods.
What you can do with it
- 1Summarize project knowledgeAsk the AI to retrieve everything you have documented regarding a specific project or topic.
- 2Review past activityRequest a summary of your journal entries from a specific timeframe to see what you accomplished.
- 3Discover knowledge connectionsIdentify the shortest path of links between two different pages in your graph.
- 4Track evolving thoughtsAnalyze how your perspective on a specific subject has changed over several months.
- 5Manage pending tasksRetrieve a list of open or stale TODO items to organize your upcoming work.
Written from the project's README. Every use case is checked against a quote from it.
LogSeq MCP tools 4
Detected from the READMEgetfindexplorecheck
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableeborden/logseq-mcp-server is public and reachablegithub.com/eborden/logseq-mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-28github.com/eborden/logseq-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model4 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubLogSeq MCP Server
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.
It never writes to your graph. Every tool only reads.
Install: see Install (Claude Code plugin, uvx, or a clone).
Who it is for
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).
What you can ask
- "What do I know about project atlas?" (a page, its blocks, related pages and what links to it)
- "What was I working on last week?" (the journal days in a period)
- "Find every block that mentions the importer and links to Alice."
- "How does project atlas connect to Bob's team page?" (the shortest path of links)
- "How did my thinking on testing change this year?" (a page over time, by month)
- "What should I work on?" (open TODOs, stale ones, an order)
The tools
10 tools in four kinds, named after what they do:
| Kind | Tools | Use for |
|---|---|---|
get |
get_page, get_block, get_current, get_graph |
One thing you can name: a page, a block, what is open now, the graph |
find |
find_blocks, find_pages |
Things that match a filter: text, page, links, property, period |
explore |
explore_context, explore_network, explore_timeline |
Walking outward from a page: context, links, time |
check |
check_links |
A gate on a [[link]] pass before you save it |
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.
Install
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.
Skills and prompts
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.
Privacy and read-only
- The server only reads. It has no tool that edits, creates or deletes anything in your graph (BR-0002).
- It talks to LogSeq on your machine (
apiUrl,127.0.0.1by default). It makes no other network calls while serving, and it logs to stderr only, never graph content. - Your token stays in
~/.logseq-mcp/config.json. Error messages never echo it. - What a client does with the results (for example, sending them to a model) is up to that client.
Learn more
- Changelog, with the v1 to v2 migration note
- Tools, prompts and resources
- Configuration
- Claude Code plugin
- Architecture, then the decisions and rules
- Development and releasing
Licensed under MIT; see LICENSE.
LogSeq MCP questions
What tools does LogSeq MCP provide?
It exposes 4 tools, including get, find, explore, check.
Can this server edit my LogSeq notes?
No, the server is strictly read-only and does not have tools to edit, create, or delete anything in your graph.
How does the server connect to my LogSeq data?
It connects via the LogSeq desktop HTTP API, which you must enable in your settings.
Is my data sent to external servers?
The server communicates with LogSeq on your local machine and makes no other network calls while serving.