Logseq MCP Tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_pagesB | |
| get_pageA | |
| create_pageA | |
| delete_pageA | |
| get_page_linked_referencesA | |
| get_page_blocksA | |
| get_blockA | |
| create_blockA | |
| insert_blockA | |
| update_blockB | |
| move_blockA | |
| remove_blockA | |
| search_blocksA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a distinct purpose targeting specific resources and actions in the Logseq graph. For example, create_block vs. insert_block clearly differentiate between creating a top-level block and inserting a child block, while get_page_blocks and search_blocks serve different retrieval functions. No tools appear to overlap in functionality.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_block, get_page, update_block). The verbs are clear and appropriate (create, get, delete, search, update, move, remove, insert), and the nouns consistently refer to Logseq entities (block, page). There are no deviations in naming conventions.
With 13 tools, this server is well-scoped for managing a Logseq graph, covering core operations without bloat. The count aligns with the domain's complexity, providing comprehensive functionality for pages and blocks (e.g., CRUD operations, hierarchical management, search) without being excessive or insufficient.
The tool set offers complete coverage for Logseq graph management, including full CRUD for pages and blocks, hierarchical operations (insert_block, move_block), search capabilities, and reference tracking. There are no obvious gaps; agents can perform all essential workflows from creation to deletion with support for linking and properties.