Logseq Model Context Protocol Agent
Logseq Model Context Protocol Agent. The logseq mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
A powerful AI assistant that connects Logseq with Claude and other LLMs using the Model Context Protocol (MCP).
Logseq MCP Agent lets AI assistants like Claude directly interact with your Logseq knowledge graph - search your notes, create content, organize information, and manage tasks.
Everything the assistant can do here goes through one of these:
Prerequisites — The Prerequisites tool exposed by this serverDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we recommend using the MCP InspectorBuilding — The Building tool exposed by this serverlogseq-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: LOGSEQ_TOKEN, LOGSEQ_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Logseq's toolset — Prerequisites, Debugging, Building — is a fair guide to whether it matches your workflow. It is maintained by briansunter; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we recommend using the MCP Inspector. |
| Building | The Building tool exposed by this server. |
{
"mcpServers": {
"logseq": {
"command": "npx",
"args": [
"logseq-mcp"
],
"env": {
"LOGSEQ_TOKEN": "your_logseq_token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOGSEQ_TOKEN | Credential the server authenticates with. | Yes |
| LOGSEQ_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.