Logseq MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGSEQ_GRAPH_PATH | Yes | The path to your Logseq graph directory |
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 |
|---|---|
| list_pagesB | Graph 내 모든 페이지 목록 조회. 각 페이지의 메타데이터(경로, 이름, 태그, 링크, 백링크) 반환 |
| read_pageC | 특정 페이지의 전체 내용과 메타데이터 조회 |
| create_pageC | 새 페이지 생성. Logseq 프로퍼티 포함 가능 |
| update_pageC | 기존 페이지 내용 수정 |
| delete_pageD | 페이지 삭제 |
| append_to_pageC | 기존 페이지 끝에 내용 추가 |
| search_pagesC | 페이지 내용/제목 검색. 태그 및 폴더 필터 지원 |
| get_backlinksC | 특정 페이지를 참조하는 모든 페이지 조회 |
| get_graphC | 페이지 간 연결 그래프 데이터 조회. 링크/백링크/태그 관계 포함 |
| get_journalC | 오늘 또는 특정 날짜의 저널 페이지 조회 |
| create_journalC | 오늘 또는 특정 날짜의 저널 페이지 생성 |
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 11 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Logseq domain, such as create_page vs. read_page vs. update_page vs. delete_page for page lifecycle, and get_backlinks vs. get_graph vs. search_pages for different query types. No tools appear to overlap or cause confusion in selection.
All tool names follow a consistent verb_noun pattern using snake_case, such as append_to_page, create_journal, and get_backlinks. This predictable naming scheme makes it easy for an agent to understand and use the tools without ambiguity or style mixing.
With 11 tools, the server is well-scoped for managing a knowledge graph like Logseq, covering essential operations from CRUD for pages and journals to advanced queries like backlinks and graph data. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides complete coverage for the Logseq domain, including full CRUD lifecycle for pages and journals, listing, reading, updating, deleting, and specialized operations like backlinks, graph retrieval, and search. There are no obvious gaps that would hinder agent workflows in this context.