v1.4.3

Bug Fixes

• Inline properties rendered as separate blocks: Consecutive key:: value lines (e.g. type:: video, source:: ..., channel:: ...) were each becoming their own block (separate bullet). They are now grouped into a single block with lines joined by \n , matching Logseq's native inline property format where all properties appear as indented lines under one bullet.

v1.4.2

Bug Fixes

• Inline properties collapsed onto one line: create_page now correctly renders each key:: value property as its own block. Previously, consecutive property lines (e.g. type:: video, source:: ..., channel:: ...) were joined into a single space-separated block. Each property is now an independent block, matching native Logseq behavior.

v1.4.1

Bug Fixes

• Page-level properties: create_page and update_page now store properties at the page entity level (createPage 2nd arg / setPageProperties) instead of on the first content block. Properties now appear in the Logseq page info panel and match (page-property ...) queries.
• Double-wrap fix: get_page_content no longer double-wraps block content that already starts with a list marker (-, *, +).

v1.4.0 - Complete Block CRUD

🧱 Block CRUD is Now Complete

v1.4.0 adds update_block, the final piece of block-level CRUD. You can now read, create, update, and delete any block by UUID.

Operation	Tool
Read	get_page_content
Create	insert_nested_block
Update	update_block ✨ new
Delete	delete_block

---

🛠️ New Tool

update_block — Edit the content of an existing block by UUID.

block_uuid  (required) — UUID of the block to edit
content     (required) — New text to replace the block's current content

Returns ✅ Successfully updated block '<uuid>' on success, ❌-prefixed message on error.

---

📦 Installation / Update

# uvx (no install needed, always latest)
uvx mcp-logseq

# or pin to this version
pip install mcp-logseq==1.4.0

---

🧪 Tests

203 tests passing. Closes #17.

v1.3.0 - 14 Tools, Bug Fixes & Reliability

🚀 What's New

v1.3.0 brings a major expansion: 14 tools (up from 6), two critical bug fixes, and a batch of reliability improvements based on thorough code review.

---

🛠️ New Tools

Tool	Description
delete_block	Remove a block by UUID
search	Full-text search across pages and blocks
query	Execute Logseq DSL queries
find_pages_by_property	Find pages by property name/value
get_pages_from_namespace	List all pages in a namespace (flat)
get_pages_tree_from_namespace	Display namespace as a hierarchy tree
rename_page	Rename a page (updates all backlinks)
get_page_backlinks	Find all pages linking to a page
insert_nested_block	Insert a block as child or sibling of an existing block

---

🐛 Bug Fixes

• LOGSEQ_API_URL not respected — all handlers were hardcoded to 127.0.0.1:12315; the env var is now properly parsed and passed to every API client
• Nested block hierarchy silently lost — _append_block_recursive was ignoring parent_uuid and flattening all blocks to root level; now uses insert_block_as_child for proper nesting
• Search snippet filtering broken — pages-content results were controlled by include_blocks instead of include_pages; snippets were also missing from the total results count
• JSON format returned Python repr — get_page_content with format=json returned str(result) instead of valid JSON
• DSL injection via property names — find_pages_by_property escaped values but not property names; property names are now validated against [a-zA-Z0-9_-]
• Duplicated HTTP call — remove_block and delete_block were identical; remove_block now delegates to delete_block

---

✨ Improvements

• LOGSEQ_VERIFY_SSL env var — control TLS verification explicitly; auto-enables for https:// URLs, disabled by default for http://
• Namespace tools now return friendly errors — previously bubbled raw exceptions; now return ❌-prefixed messages like other tools

---

📦 Installation

# With uvx (recommended, no install needed)
claude mcp add-json mcp-logseq '{
  "command": "uvx",
  "args": ["mcp-logseq"],
  "env": {
    "LOGSEQ_API_TOKEN": "your_token",
    "LOGSEQ_API_URL": "http://localhost:12315"
  }
}'

# Or with pip
pip install mcp-logseq==1.3.0

---

🧪 Tests

195 tests passing. New coverage added for:

• InsertNestedBlockToolHandler (5 tests)
• insert_block_as_child (3 tests)
• _append_block_recursive root/nested/children paths (3 tests)
• Integration test now verifies all 14 handlers are registered

v1.0.1 - Critical Fixes and UX Improvements

🔧 Critical Fixes & Major UX Improvements

🐛 Bug Fixes

• Fix server crash due to file logging permission errors on read-only filesystems
• Improve logging reliability with user cache directory (~/.cache/mcp-logseq/) and fallback handling

🚀 Major UX Improvements

• Zero installation required! Now uses uv --with for automatic dependency management
• Simplified setup - no more pip install step needed
• Enhanced documentation with comprehensive troubleshooting for PATH issues in Claude Desktop

📚 Documentation Updates

• Complete installation guide rewrite using uv best practices
• Added troubleshooting section for spawn uv ENOENT errors
• Updated DEVELOPMENT.md with proper entry points
• Provided full path solutions for different uv installation methods

🔄 Breaking Change (Installation Only)

The recommended installation method has changed from pip install to uv --with. The old method still works, but the new method is more reliable and requires no pre-installation.

New recommended setup:

claude mcp add mcp-logseq \
  --env LOGSEQ_API_TOKEN=your_token \
  -- uv run --with mcp-logseq mcp-logseq

📦 What's Included

• Fixed file logging permissions (server.py:18-35)
• Zero-dependency installation workflow
• Comprehensive PATH troubleshooting guide

v1.0.0 - First stable release

🎉 First stable release of mcp-logseq!

Features

• Complete MCP server for LogSeq integration
• 6 comprehensive tools: create_page, list_pages, get_page_content, delete_page, update_page, search
• Full LogSeq API integration via local HTTP server
• Comprehensive documentation and examples
• Complete test suite (unit + integration tests)

Installation

pip install mcp-logseq

Compatibility

• Python 3.11+
• LogSeq with HTTP API enabled
• Works with Claude Code and Claude Desktop

What's Next

This release marks the stable API for mcp-logseq. Future releases will focus on enhancements while maintaining backward compatibility.

🔗 PyPI: https://pypi.org/project/mcp-logseq/
📚 Documentation: See README.md for setup instructions