logseq.get_all_pagesLABSCO SUMMARY
Your notes graph, writable from the conversation.
Read-only note access is common; the block-level writes are what make this different. An assistant can insert a child block under the right parent instead of appending text to the bottom of a page.
What it is
An MCP server that talks to a running Logseq instance over its local API. Tools sit under a logseq namespace and split into pages and blocks, which is how Logseq itself is structured.
What you get
- Every page in the graph listed, and any single page fetched
- Pages created, and deleted along with their blocks
- All blocks on a page read, or one block by ID
- Blocks created on a page, or inserted as a child of another block
- Blocks updated, moved and removed with their children
- Blocks searched by query across the whole graph
Requirements
A recent Python, and Logseq with Developer mode on, the Logseq Developer Plugin enabled and an API token set in Advanced settings — then restart Logseq. The server reads LOGSEQ_API_URL, http://localhost:12315 in the standard setup, and LOGSEQ_TOKEN.
Setup effort
One command plus a local token — uvx logseq-mcp, then supply the token
USE CASES
01
Filing what you just worked out into the right note
Create the block on the page, or insert it under the parent it belongs to.
02
Finding where you wrote about this before
Search blocks across the graph instead of opening pages one at a time.
03
Summarising a page you have been adding to for months
Read all of its blocks in one call.
04
Starting a page for a new project
Create the page, then add its first blocks.
05
Reorganising an outline that got tangled
Move blocks under different parents and reword the ones that need it.
06
Clearing out notes you no longer keep
Remove the block with its children, or delete the page outright.
12 tools
Listed in project docs. Your client may show a different list.
logseq.get_pagelogseq.create_pagelogseq.delete_pagelogseq.get_page_blockslogseq.get_blocklogseq.create_blocklogseq.insert_blocklogseq.update_blocklogseq.move_blocklogseq.remove_blocklogseq.search_blocksBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- uvx on PATH
- LOGSEQ_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx logseq-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"logseq": {
"command": "uvx",
"args": [
"logseq-mcp"
],
"env": {
"LOGSEQ_API_URL": "http://localhost:12315",
"LOGSEQ_TOKEN": "<YOUR_LOGSEQ_TOKEN>"
}
}
}
}<YOUR_LOGSEQ_TOKEN> is the API token you set in Logseq's Advanced settings. If Cursor cannot find uvx, use its full path from which uvx (the README's example is /opt/homebrew/bin/uvx).
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --env LOGSEQ_API_URL=http://localhost:12315 --env LOGSEQ_TOKEN=<YOUR_LOGSEQ_TOKEN> --transport stdio logseq -- uvx logseq-mcp
