v1.0.2 — Live Context Tools + Claude Code CLI Integration

What's New

5 New Live Context Tools

Claude Code CLI now knows what you're looking at in Logseq — no companion plugin required. All new tools call Logseq's existing HTTP API at :12315 which proxies plugin-level UI state directly.

Tool	What it returns
get_current_page	Active page name, UUID, and type (journal/standard)
get_current_block	Block UUID and content where cursor is positioned
get_editing_selection	All currently selected blocks with content
get_current_graph	Graph name and filesystem path
suggest_workspace	Pre-filled .mcp.json + one-liner install command

Self-Guiding Setup via suggest_workspace

From inside any Claude session, ask: "how do I set up Claude Code with my Logseq graph?"

Claude calls suggest_workspace, which reads your active graph path and active token, then returns:

• A .mcp.json file to drop in your graph folder (auto-connects on every claude run)
• A one-liner claude mcp add-json command for global registration

uvx Install — No PyPI Required

claude mcp add-json logseq '{"command":"uvx","args":["git+https://github.com/gustavo-meilus/logseq-api-mcp"],"env":{"LOGSEQ_API_TOKEN":"<your-token>","LOGSEQ_API_URL":"http://127.0.0.1:12315"}}'

Auto-Connect via .mcp.json in Graph Folder

Drop this in your Logseq graph folder and claude auto-connects all 26 tools on startup:

{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": ["git+https://github.com/gustavo-meilus/logseq-api-mcp"],
      "env": {
        "LOGSEQ_API_TOKEN": "<your-token>",
        "LOGSEQ_API_URL": "http://127.0.0.1:12315"
      }
    }
  }
}

Stats

• 26 tools total (was 21)
• 424 tests passing (was 379, +45 new)
• Zero mypy errors, zero lint warnings

Prerequisites

• Logseq desktop with Enable HTTP APIs server turned on (Settings → Features)
• API token from the Logseq API panel
• uvx installed (curl -LsSf https://astral.sh/uv/install.sh | sh)