You can connect a Logseq graph to Claude two ways: through Logseq’s own HTTP API, or by pointing the Filesystem MCP server at your graph folder. They suit different people, and picking the wrong one is why a lot of setups feel disappointing.
Logseq doesn’t ship an MCP server of its own, so every option here is community-built. Start with the Filesystem route unless you know you need block-level access.
- No official server exists. Everything is community-built, discussed on the Logseq forum and subreddit.
- Two routes. The Logseq HTTP API for block-level access, or Filesystem MCP for the raw markdown.
- Filesystem is the easier start. No token, no API server, works with Logseq closed.
- Check your Logseq version first. File-based and database graphs do not behave the same way.
Filesystem MCP or the HTTP API
- You mostly want to search and read your notes.
- You want it working in five minutes with no token.
- You want access whether or not Logseq is open.
- You already use Filesystem MCP for other folders.
- You need block references resolved, not shown as syntax.
- You want the assistant appending to journals correctly.
- You rely on Logseq queries and want those results.
- You are happy keeping Logseq running with the API on.
How to connect Logseq with Filesystem MCP
On the file-based version of Logseq, your graph is a folder of markdown files, with pages in one directory, journals in another and assets alongside them. The standard Filesystem MCP server already does most of what you want. Point it at your graph directory and Claude can read every note, search across them and write new ones.
The limit is that Claude sees plain text files and none of Logseq’s graph structure. Block references, page links and queries are plain markdown syntax to a filesystem reader. It can see ((block-ref)) sitting in a line, but it can’t resolve what that block says. For everyday questions about the content of your notes, that’s fine.
How to connect Logseq with the HTTP API
Logseq ships an HTTP API server you turn on yourself. MCP servers built against it get Logseq’s own model of your graph. That allows block-level operations: reading a block and its children, following references properly, running Logseq queries, and appending to today’s journal in the right place.
- In Logseq, open Settings, then Features, and check Enable HTTP APIs server.
- Click the API button, choose Start server, and create a token under Authorization tokens.
- Add the server to your MCP client. For ergut/mcp-logseq, which needs uv installed, put this block in
claude_desktop_config.json, or run the equivalentclaude mcp addcommand from the project’s README for Claude Code. Codex usesconfig.toml. - Restart the client so it reloads the config.
{
"mcpServers": {
"mcp-logseq": {
"command": "uv",
"args": ["run", "--with", "mcp-logseq", "mcp-logseq"],
"env": {
"LOGSEQ_API_TOKEN": "your_token_here",
"LOGSEQ_API_URL": "http://localhost:12315"
}
}
}
}
The cost is that Logseq has to be running with the API server on, you’re passing a token around your config, and you’re depending on a community server keeping pace with Logseq’s changes.
Which Logseq MCP server to use
ergut/mcp-logseq is the most frequently referenced option and works against the HTTP API. Try it first if you’ve chosen the API route.
joelhooks/logseq-mcp-tools and dailydaniel/logseq-mcp are the other two that come up regularly in the community listings, with similar goals and different design choices.
All three are free and open source, and none has a support desk. The ecosystem is smaller and less settled than Obsidian’s, which has its own comparison of servers. Tana went the other way and shipped the server inside its desktop app, which takes the maintainer question off the table.
Does it work with the database version of Logseq?
Check this before you spend an evening on setup. Logseq’s long-running move from a file-based graph to a database-backed one breaks the assumption every filesystem approach rests on. If your graph isn’t a folder of markdown files, pointing Filesystem MCP at it won’t do what you expect.
Servers built on the HTTP API are better placed, because they ask Logseq for data instead of reading its storage. The ergut/mcp-logseq README lists opt-in support for database-mode graphs. Community servers move at community speed, though, so read the server’s README against your Logseq version. The Logseq forum has active threads on exactly this.
What to ask Claude once it’s connected
The daily journal is what makes Logseq different from a notes app, and it’s where connecting an assistant pays off fastest.
- Mine your journals: “What did I write about this project across all my daily notes?”
- Find the thread: “Which of my notes connect to this idea, even if I did not link them?”
- Weekly review: “Summarize what I worked on in the last seven days of journals.”
- Catch the loose ends: “Find TODO blocks I created more than a month ago and never closed.”
- Write into the graph: “Add these three points to today’s journal under a Research heading.” The API route handles this properly. Filesystem will append text and get the nesting approximately right.
Limits to expect
The ecosystem is thin. Fewer servers, fewer maintainers, and more chance that the one you pick lags a Logseq release. It could be worse: every top-ranked OneNote server has been abandoned.
Everything in one graph means everything is visible. If you keep journals, work notes and personal thinking in one graph, connecting it connects all of that. Split anything sensitive into a separate graph you don’t point the server at. Filesystem access stays local, and the HTTP API runs on your own machine rather than in the cloud.
Large graphs get slow. Thousands of pages read through a filesystem server won’t be instant. Scope the query when you can.
Adding the things you saved
Logseq holds what you wrote. ContextBolt holds what you saved: threads from X, Reddit and LinkedIn posts, and articles you meant to come back to, each kept with its text. It’s a Chrome extension. Saves are AI-tagged and clustered into topics on arrival, and on Pro the library gets its own MCP endpoint, so Claude can search your saved reading by meaning in the same conversation it searches your graph.
It isn’t a Logseq plugin and it doesn’t write into your graph. The two servers run side by side in the same agent. Basic is free up to 150 bookmarks. Pro is $6 a month, removes the cap, and includes the endpoint.