The Logseq MCP Server enables AI assistants like Claude to directly read, write, and navigate your local Logseq knowledge graph through the Model Context Protocol.
Page Management (CRUD):
List all pages with metadata (tags, links, backlinks), filtered by
pagesorjournalsfoldersRead, create, update, delete, and append content to pages
Full support for Logseq properties and metadata
Search & Discovery:
Full-text search across page content and titles
Filter results by tags and folders
Get backlinks to see all pages referencing a specific page
Traverse the knowledge graph with configurable depth and center points
Journal Operations:
Access and create daily journals for today or any specific date
Create entries with optional templates
Log structured content: articles (with title, summary, tags, URL, highlights), books (with title, author, tags, memo), movies (with title, director, memo), and exhibitions (with title, venue, artist, memo)
Key Features:
Direct filesystem access to local Logseq graphs (Markdown format, not Logseq Sync)
Security protections against path traversal and injection attacks
Korean language optimizations (weather integration, cultural content templates)
Exposes graph pages as MCP resources for AI context
Use Cases: Automated note-taking during conversations, searching and summarizing past entries, managing TODO items, building knowledge connections, and logging media consumption.
Enables AI assistants to directly read, write, and manage Logseq graphs, including creating and modifying pages, searching content, navigating backlinks and page relationships, and managing journal entries with template support.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Logseq MCP Server오늘 저널에 '오후 3시 팀 회의' 추가해줘"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Logseq MCP Server
Let AI read and write your Logseq graph directly via MCP
Talk to Claude and say "add this to today's journal", "find what I did last week", "show me all pages linked to this one" - and it just works.
Why This?
Problem: Logseq is a great PKM tool, but integrating with AI assistants requires constant copy-pasting.
Solution: With this MCP server:
Claude directly writes to your journal (no copy-paste)
Search and summarize past entries (maintain context)
Navigate connections between pages (backlinks, graph)
Auto-generate daily journals with templates
Is This For You?
Good fit if you...
Use Logseq as your primary PKM
Use Claude Code or Claude Desktop regularly
Want to delegate note management to AI
Use local file-based Logseq (not Logseq Sync)
Not for you if...
Using Logseq Sync (requires local file access)
Obsidian user (different MCP server needed)
Have sensitive info in notes and uncomfortable with AI access
Use org-mode instead of Markdown (not yet supported)
Features
Feature | Description |
Page CRUD | Create, read, update, delete pages + property support |
Search | Full-text search + tag/folder filtering |
Graph Navigation | Links, backlinks, page relationship traversal |
Journal | Access today's/specific date journals + templates |
Content Logging | Log articles, books, movies, exhibitions to journal |
Resources | Expose graph pages as MCP resources |
Quick Start
1. Install
2. Configure
Claude Code (~/.claude/settings.json):
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
3. Verify
Ask Claude: "Show me my Logseq page list"
Available Tools
Tool | Description |
| List all pages with metadata (tags, links, backlinks) |
| Read page content and metadata |
| Create new page (with property support) |
| Update page content |
| Delete a page |
| Append content to existing page |
| Search by content/title + tag/folder filters |
| Get pages that reference a specific page |
| Get page connection graph data |
| Get today's or specific date's journal |
| Create journal with optional template |
| Add article to journal (title, summary, tags, URL, highlights) |
| Add book to journal (title, author, tags, memo) |
| Add movie to journal (title, director, memo) |
| Add exhibition to journal (title, venue, artist, memo) |
Usage Examples
Logseq Graph Structure
Security
Path traversal protection (graph-only access)
Symlink/hardlink attack prevention
Input validation and sanitization
DoS protection (content size limits)
Error message sanitization
Troubleshooting
"LOGSEQ_GRAPH_PATH environment variable is required"
Set LOGSEQ_GRAPH_PATH in your configuration file.
MCP server not recognized by Claude
Restart Claude Code/Desktop
Verify path is absolute (
/Users/...format)Ensure
npm run buildwas executed
Pages not showing up
Check if
.mdfiles exist injournals/orpages/Verify you're using local graph (not Logseq Sync)
org-mode files not reading
Currently Markdown only. org-mode support planned for future.
Korean-Specific Features
This project includes features optimized for Korean users:
Daily Automation (Optional)
Auto-generate daily journal with weather (Korea only - uses Naver Weather) and diary template.
Copy and edit plist file:
Load launchd agent:
Test manually:
Generated template structure:
See Korean README for more details.
Cultural Content Structure
add_book, add_movie, add_exhibition tools use Korean wikilink structure ([[문화]]). Customize the templates in src/index.ts for your language.
Development
Project Structure
Contributing
Issues and PRs welcome!
Fork this repo
Create feature branch (
git checkout -b feature/amazing)Commit changes (
git commit -m 'Add amazing feature')Push to branch (
git push origin feature/amazing)Open a Pull Request
Ideas for contribution
org-mode support
Logseq property search
Whiteboard support
Better graph visualization data
i18n for templates
License
Polyform Noncommercial 1.0.0 - Free for personal and noncommercial use.