Skip to main content

MCP server to work with LogSeq via the local HTTP server

Project description

MCP LogSeq

MCP server for LogSeq

MCP server to interact with LogSeq via its API. Enables Claude to read, create, and manage LogSeq pages through a comprehensive set of tools.

✨ What You Can Do

Transform your LogSeq knowledge base into an AI-powered workspace! This MCP server enables Claude to seamlessly interact with your LogSeq graphs.

🎯 Real-World Examples

📊 Intelligent Knowledge Management

"Analyze all my project notes from the past month and create a status summary"
"Find pages mentioning 'machine learning' and create a study roadmap"
"Search for incomplete tasks across all my pages"

📝 Automated Content Creation

"Create a new page called 'Today's Standup' with my meeting notes"
"Add today's progress update to my existing project timeline page"  
"Create a weekly review page from my recent notes"

🔍 Smart Research & Analysis

"Compare my notes on React vs Vue and highlight key differences"
"Find all references to 'customer feedback' and summarize themes"
"Create a knowledge map connecting related topics across pages"

🤝 Meeting & Documentation Workflow

"Read my meeting notes and create individual task pages for each action item"
"Get my journal entries from this week and create a summary page"
"Search for 'Q4 planning' and organize all related content into a new overview page"

💡 Key Benefits

  • Zero Context Switching: Claude works directly with your LogSeq data
  • Preserve Your Workflow: No need to export or copy content manually
  • Intelligent Organization: AI-powered page creation, linking, and search
  • Enhanced Productivity: Automate repetitive knowledge work

🚀 Quick Start

Step 1: Enable LogSeq API

  1. SettingsFeatures → Check "Enable HTTP APIs server"
  2. Click the API button (🔌) in LogSeq → "Start server"
  3. Generate API token: API panel → "Authorization tokens" → Create new

Step 2: Add to Claude (No Installation Required!)

Claude Code

claude mcp add mcp-logseq \
  --env LOGSEQ_API_TOKEN=your_token_here \
  --env LOGSEQ_API_URL=http://localhost:12315 \
  -- uv run --with mcp-logseq mcp-logseq

Claude Desktop

Add to your config file (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "mcp-logseq": {
      "command": "uv",
      "args": ["run", "--with", "mcp-logseq", "mcp-logseq"],
      "env": {
        "LOGSEQ_API_TOKEN": "your_token_here",
        "LOGSEQ_API_URL": "http://localhost:12315"
      }
    }
  }
}

Step 3: Start Using!

"Please help me organize my LogSeq notes. Show me what pages I have."

🛠️ Available Tools

The server provides 15 tools with intelligent markdown parsing:

Tool Purpose Example Use
list_pages Browse your graph "Show me all my pages"
get_page_content Read page content "Get my project notes"
create_page Add new pages with structured blocks "Create a meeting notes page with agenda items"
update_page Modify pages (append/replace modes) "Update my task list"
delete_page Remove pages "Delete the old draft page"
delete_block Remove a block by UUID "Delete this specific block"
update_block Edit block content by UUID "Update this specific block text"
search Find content across graph "Search for 'productivity tips'"
query Execute Logseq DSL queries "Find all TODO tasks tagged #project"
find_pages_by_property Search pages by property "Find all pages with status = active"
get_pages_from_namespace List pages in a namespace "Show all pages under Customer/"
get_pages_tree_from_namespace Hierarchical namespace view "Show Projects/ as a tree"
rename_page Rename with reference updates "Rename 'Old Name' to 'New Name'"
get_page_backlinks Find pages linking to a page "What links to this page?"
insert_nested_block Insert child/sibling blocks "Add a child block under this task"

🎨 Smart Markdown Parsing (v1.1.0+)

The create_page and update_page tools now automatically convert markdown into Logseq's native block structure:

Markdown Input:

---
tags: [project, active]
priority: high
---

# Project Overview
Introduction paragraph here.

## Tasks
- Task 1
  - Subtask A
  - Subtask B
- Task 2

## Code Example
```python
def hello():
    print("Hello Logseq!")

**Result:** Creates properly nested blocks with:
- ✅ Page properties from YAML frontmatter (`tags`, `priority`)
- ✅ Hierarchical sections from headings (`#`, `##`, `###`)
- ✅ Nested bullet lists with proper indentation
- ✅ Code blocks preserved as single blocks
- ✅ Checkbox support (`- [ ]` → TODO, `- [x]` → DONE)

**Update Modes:**
- **`append`** (default): Add new content after existing blocks
- **`replace`**: Clear page and replace with new content

---

## ⚙️ Prerequisites

### LogSeq Setup
- **LogSeq installed** and running
- **HTTP APIs server enabled** (Settings → Features)
- **API server started** (🔌 button → "Start server")  
- **API token generated** (API panel → Authorization tokens)

### System Requirements
- **[uv](https://docs.astral.sh/uv/)** Python package manager
- **MCP-compatible client** (Claude Code, Claude Desktop, etc.)

---

## 🔧 Configuration

### Environment Variables
- **`LOGSEQ_API_TOKEN`** (required): Your LogSeq API token
- **`LOGSEQ_API_URL`** (optional): Server URL (default: `http://localhost:12315`)

### Alternative Setup Methods

#### Using .env file
```bash
# .env
LOGSEQ_API_TOKEN=your_token_here
LOGSEQ_API_URL=http://localhost:12315

System environment variables

export LOGSEQ_API_TOKEN=your_token_here
export LOGSEQ_API_URL=http://localhost:12315

🔍 Verification & Testing

Test LogSeq Connection

uv run --with mcp-logseq python -c "
from mcp_logseq.logseq import LogSeq
api = LogSeq(api_key='your_token')
print(f'Connected! Found {len(api.list_pages())} pages')
"

Verify MCP Registration

claude mcp list  # Should show mcp-logseq

Debug with MCP Inspector

npx @modelcontextprotocol/inspector uv run --with mcp-logseq mcp-logseq

🐛 Troubleshooting

Common Issues

"LOGSEQ_API_TOKEN environment variable required"

  • ✅ Enable HTTP APIs in Settings → Features
  • ✅ Click 🔌 button"Start server" in LogSeq
  • ✅ Generate token in API panel → Authorization tokens
  • ✅ Verify token in your configuration

"spawn uv ENOENT" (Claude Desktop)

Claude Desktop can't find uv. Use the full path:

which uv  # Find your uv location

Update config with full path:

{
  "mcpServers": {
    "mcp-logseq": {
      "command": "/Users/username/.local/bin/uv",
      "args": ["run", "--with", "mcp-logseq", "mcp-logseq"],
      "env": { "LOGSEQ_API_TOKEN": "your_token_here" }
    }
  }
}

Common uv locations:

  • Curl install: ~/.local/bin/uv
  • Homebrew: /opt/homebrew/bin/uv
  • Pip install: Check with which uv

Connection Issues

  • ✅ Confirm LogSeq is running
  • ✅ Verify API server is started (not just enabled)
  • ✅ Check port 12315 is accessible
  • ✅ Test with verification command above

👩‍💻 Development

For local development, testing, and contributing, see DEVELOPMENT.md.


Ready to supercharge your LogSeq workflow with AI?

Star this repo if you find it helpful!

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mcp_logseq-1.4.3.tar.gz (913.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mcp_logseq-1.4.3-py3-none-any.whl (26.4 kB view details)

Uploaded Python 3

File details

Details for the file mcp_logseq-1.4.3.tar.gz.

File metadata

  • Download URL: mcp_logseq-1.4.3.tar.gz
  • Upload date:
  • Size: 913.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.8.22

File hashes

Hashes for mcp_logseq-1.4.3.tar.gz
Algorithm Hash digest
SHA256 a8eb268d30a50c8c8f943e46fd21dc7415721e74a4a1b695493bd1886dac0268
MD5 d59d95dd35f7cc0eb0982deabcb7b40c
BLAKE2b-256 0f5268209fe3548f4a987ddbd32e44f66d622674540b1aa514e3284d5305b059

See more details on using hashes here.

File details

Details for the file mcp_logseq-1.4.3-py3-none-any.whl.

File metadata

  • Download URL: mcp_logseq-1.4.3-py3-none-any.whl
  • Upload date:
  • Size: 26.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.8.22

File hashes

Hashes for mcp_logseq-1.4.3-py3-none-any.whl
Algorithm Hash digest
SHA256 153c1ab4cfb2017d7251dcfc2021d2705070aff0640aa58f24782a7672ab38c4
MD5 4bd3a495fcf9ae4652ce7d3d4f7cd91c
BLAKE2b-256 f8c6f64a2124060c4fde9b257a50cbd048bd7a076a64276fbd677109f48e687e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page