logseq-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGSEQ_API_HOST | No | Logseq API host (default: localhost) | localhost |
| LOGSEQ_API_PORT | No | Logseq API port (default: 12315) | 12315 |
| LOGSEQ_MCP_DEBUG | No | Enable console output (set to 'true' to enable, default: false) | false |
| LOGSEQ_MCP_LOG_FILE | No | Custom log file path (optional) | |
| LOGSEQ_MCP_LOG_MODE | No | Logging mode: privacy, debug, minimal (default: privacy) | privacy |
| LOGSEQ_MCP_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR (default: INFO) | INFO |
| LOGSEQ_MCP_TRANSPORT | No | Transport mode: stdio or sse (default: stdio) | stdio |
| LOGSEQ_DELETE_ENABLED | No | Enable delete_block tool (set to 'true' to enable, default: false) | false |
| LOGSEQ_MCP_LOG_MAX_SIZE | No | Max log file size before rotation (default: 10MB) | 10MB |
| LOGSEQ_MCP_PROJECT_ROOT | No | Absolute path to the project directory for log storage | |
| LOGSEQ_MCP_LOG_RETENTION_DAYS | No | Days to keep logs before automatic deletion (optional) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_blockB | Create a new block in Logseq |
| update_blockB | Update an existing block in Logseq |
| create_pageB | Create a new page in Logseq |
| get_all_pagesB | Get all pages in the current Logseq graph |
| get_pageC | Get a page from Logseq by name |
| get_journal_pageA | Get a journal page by date. Automatically converts the date to Logseq's journal format. |
| search_pagesC | Search for pages in Logseq |
| execute_queryB | Execute a Datalog query in Logseq |
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 8 tools
Each tool targets a distinct operation: page retrieval, page creation, block creation/update, journal fetching, search, and querying. The only potentially related tools are get_page, get_all_pages, and search_pages, but their purposes are clearly differentiated by exact-match retrieval, full listing, and search.
All tools follow a consistent verb_noun pattern in snake_case, such as create_block, get_page, search_pages, and execute_query. The naming convention is uniform and predictable throughout the entire set.
Eight tools is well-scoped for a Logseq MCP server, covering page management, block manipulation, search, and querying without unnecessary bloat. Each tool has a clear role in the surface.
The server covers creation and reading for pages and creation/update for blocks, but missing operations like page update/delete, block delete, or block retrieval create notable gaps. Agents can work around some of these via execute_query, but lifecycle coverage is incomplete.