A fairly customizable MCP server for Logseq
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A fairly customizable MCP server for Logseq. The mcp mcp server is what makes that connection.
A MCP server for interacting with your Logseq Personal Knowledge Management system using custom instructions
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Resources — The Resources tool exposed by this serverTools — The Tools tool exposed by this serverDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPConfiguration is passed through the environment: LOGSEQ_API_TOKEN, LOGSEQ_URL, LOGSEQ_API_KEY, UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Resources, Tools, Debugging — is a fair guide to whether it matches your workflow. It is maintained by ruliana; 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 |
|---|---|
| Resources | The Resources tool exposed by this server. |
| Tools | The Tools tool exposed by this server. |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
"mcpServers": {
"mcp-pkm-logseq": {
"command": "uvx",
"args": [
"mcp-pkm-logseq"
],
"env": {
"LOGSEQ_API_TOKEN": "your-logseq-api-token",
"LOGSEQ_URL": "http://localhost:12315"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOGSEQ_API_TOKEN | Credential the server authenticates with. | Yes |
| LOGSEQ_URL | Endpoint or connection string the server talks to. | Yes |
| LOGSEQ_API_KEY | Credential the server authenticates with. | Yes |
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
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.