logseq-mcp-server
A read-only MCP server for LogSeq graphs. It gives an AI client 16 tools to search a graph, follow links, build context for a topic and read journals by date. It never writes to the graph.
This package is the server itself: one native Rust binary, with no Python code and no runtime dependencies. It is the same binary, byte for byte, as the one on the project's GitHub Releases. The wheels are built and attested by the release workflow, attached to the release beside the binaries, and uploaded here from there once the release is public.
Install
Wheels exist for macOS (Apple silicon and Intel) and Linux (x86_64, glibc and musl). There is no Windows wheel yet, so installing on Windows fails with "no matching distribution".
uvx logseq-mcp-server # run it without installing
uv tool install logseq-mcp-server
pipx install logseq-mcp-server
Set up LogSeq
-
In LogSeq, turn on the HTTP API server (Settings, then API) and generate an auth token.
-
Create
~/.logseq-mcp/config.json:{ "apiUrl": "http://127.0.0.1:12315", "authToken": "your-token-here" }
The server reads its token from that file, so no credentials go in your client's config.
Connect a client
Claude Desktop (claude_desktop_config.json), or any client that starts MCP servers over stdio:
{
"mcpServers": {
"logseq": {
"command": "uvx",
"args": ["logseq-mcp-server"]
}
}
}
Claude Code:
claude mcp add logseq -- uvx logseq-mcp-server
More
The tools, the options (timeoutMs, tips, LOGSEQ_MCP_CONFIG), the Claude Code plugin with skills, and the design notes are in the project README. Report problems on the issue tracker.
Licensed under MIT. The licences of the crates inside the binary are in THIRD-PARTY-NOTICES.txt, installed in the package's .dist-info/licenses directory.
Metadata
Release files for logseq-mcp-server 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| logseq_mcp_server-1.0.0-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64, Linux musl 1.2+ x86-64 | Details |
| logseq_mcp_server-1.0.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| logseq_mcp_server-1.0.0-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 6.9 MB
Release files / logseq_mcp_server-1.0.0-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl
| Download URL | logseq_mcp_server-1.0.0-py3-none-manylinux_2_17_x86_64.musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | Linux glibc 2.17+ x86-64 Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
4ce04800a1cf84a34fc0cb436bbd5a5272ee59a85902ee9b6f2549d7fc78ab48
|
|
BLAKE2b-256 checksum How to use checksums |
1b4a39ab5700a65236f68d743e6574138a6133139053dd589ef94304f83c9843
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / logseq_mcp_server-1.0.0-py3-none-macosx_11_0_arm64.whl
| Download URL | logseq_mcp_server-1.0.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6b346960446e079c3012d9ad5e0c509db4cbdb5fb3bdb92a74f6c0ac5de4c932
|
|
BLAKE2b-256 checksum How to use checksums |
4ee9e57b224f5f585228f6ddcac93e92cefcce376460db80dc5f33b16163286a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / logseq_mcp_server-1.0.0-py3-none-macosx_10_12_x86_64.whl
| Download URL | logseq_mcp_server-1.0.0-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
c5e8b2ed9478fe77c42d1a395a10b9523e7fbbbfbbe726f6a374d3563e23af3d
|
|
BLAKE2b-256 checksum How to use checksums |
e01a03bfafc46bd95e0269357bc6a4d623f54e75ffe5311bd754d0d5ebcc8f52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log