Logseq MCP Server
Reads, writes and queries a Logseq graph over its local HTTP API, down to individual blocks.
Add it to your client
Communityuv run --with mcp-logseq mcp-logseq
{
"mcpServers": {
"logseq-mcp": {
"command": "uv",
"args": [
"run",
"--with",
"mcp-logseq",
"mcp-logseq"
]
}
}
}- Transport
- stdio
- Runtime
- Python
- Auth
- Required
- Tools
- 16
- License
- MIT
- Stars
- 323
Logseq stores an outline, not a pile of documents, and the interesting part of this server is that it respects that: besides page-level create, update, rename and delete, it edits and inserts blocks by UUID, sets block properties on DB-mode graphs, runs Logseq's own DSL queries, and walks namespaces as a tree. Sixteen tools cover that ground, with three more behind an optional vector index. Setup is the usual Logseq trip — enable the HTTP APIs server in Features, start it from the API panel, mint an authorization token. Semantic search is opt-in; LanceDB stays local, but a hosted embedding provider sees the note text you index.
Similar MCP servers
Grounded Docs MCP Server
MCP serverIndexes library documentation locally so queries answer for the version actually in your lockfile.
Buildkite MCP Server
MCP serverQuery Buildkite pipelines, builds, jobs and test runs from an agent session.
Blockscout MCP Server
MCP serverBlockscout's official server for explorer data — balances, tokens, NFTs and contract metadata across many chains.

Comments(0)
Sign in to comment