A MCP server that uses Logseq API to extract and interact with Logseq notes.
Most developer tooling work still happens through a UI a human drives. Logseq API MCP server moves it into the conversation instead. A MCP server that uses Logseq API to extract and interact with Logseq notes.
The server publishes 14 tools. What each one is for:
get_all_pages — Every page with ID, UUID, journal flag, and namespaceget_page_blocks — Hierarchical block tree with IDs, UUIDs, and child countsget_page_links — Pages linking to a target pageget_page_backlinks — Full backlink analysis including block-level referencesget_block_content — Block detail with properties and immediate childrenget_all_page_content — Complete page: properties, blocks, DB refs expandedget_linked_flashcards — Q&A flashcard pairs from a page and all linked pagessearch — Full-text search across blocks, pages, and file namesquery — Raw Datalog / DSL queries against the graphfind_pages_by_property — Filter pages by property key and optional valueget_pages_from_namespace — All pages under a Logseq namespaceget_pages_tree_from_namespace — Nested tree of namespace pagesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: LOGSEQ_API_ENDPOINT, LOGSEQ_API_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.
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 API's toolset — get_all_pages, get_page_blocks, get_page_links and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gustavo-meilus; 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 |
|---|---|
| get_all_pages | Every page with ID, UUID, journal flag, and namespace |
| get_page_blocks | Hierarchical block tree with IDs, UUIDs, and child counts |
| get_page_links | Pages linking to a target page |
| get_page_backlinks | Full backlink analysis including block-level references |
| get_block_content | Block detail with properties and immediate children |
| get_all_page_content | Complete page: properties, blocks, DB refs expanded |
| get_linked_flashcards | Q&A flashcard pairs from a page and all linked pages |
| search | Full-text search across blocks, pages, and file names |
| query | Raw Datalog / DSL queries against the graph |
| find_pages_by_property | Filter pages by property key and optional value |
| get_pages_from_namespace | All pages under a Logseq namespace |
| get_pages_tree_from_namespace | Nested tree of namespace pages |
| create_page | Create a page with optional properties and format |
| delete_page | Remove a page permanently |
// ~/.claude/claude_desktop_config.json
{
"mcpServers": {
"logseq-api": {
"command": "uv",
"args": ["run", "--directory", "/path/to/logseq-api-mcp", "python", "src/server.py"],
"env": {
"LOGSEQ_API_ENDPOINT": "http://127.0.0.1:12315/api",
"LOGSEQ_API_TOKEN": "your_token_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOGSEQ_API_ENDPOINT | Configuration value read at startup. | Optional |
| LOGSEQ_API_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.