Agent skill · software engineering · aiskillstore
connecting-to-logseq
Manages connections to Logseq graphs via HTTP API, CLI, or MCP Server. Auto-invokes when users mention connecting to Logseq, API tokens, graph paths, connection issues, or backend configuration. Handles backend detection, environment setup, and connectivity troubleshooting.
Why this skill is useful
Provides specific commands and setup procedures for connecting to Logseq via HTTP API, CLI, and MCP Server that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Connecting to Logseq When to Use This Skill This skill auto-invokes when: User wants to connect Claude to their Logseq graph Setting up Logseq integration or API tokens Troubleshooting connection issues Configuring graph paths or backends User mentions "connect to logseq", "logseq api", "logseq token" Questions about HTTP API, CLI, or MCP server setup Setup Scripts: See {baseDir}/scripts/ for initialization utilities. Available Backends Backend Requires Logseq Running Read Write Best For --------- ------------------------ ------ ------- ---------- HTTP API Yes Full Full Real-time, interactive CLI No Full Limited Offline, batch, CI/CD MCP Server Yes (via HTTP) Full Full Claude-native tools Quick Start 1. Enable Logseq HTTP API In Logseq: 1. Settings → Advanced → Developer mode: ON 2. Settings → Advanced → HTTP APIs server: ON 3. Settings → Advanced → Authorization tokens → Create token 2. Set Environment Variable 3. Initialize Plugin Run the setup wizard: Or use the command: /logseq:init Backend Details HTTP API (Primary) URL: http://127.0.0.1:12315/api Request Format: Common Methods: logseq.App.getCurrentGraph - Get current graph info logseq.Editor.getPage - Get page by name logseq.Editor.getBlock - Get block by UUID logseq.DB.datascriptQuery - Execute Datalog query logseq.Editor.insertBlock - Create new block CLI (@logseq/cli) Installation: Usage: MCP Server The plugin includes a custom MCP server that exposes Logseq operations as Claude tools. Location: servers/logseq-mcp/ Build: Configuration File Location: .claude/logseq-expert/env.json Troubleshooting "Cannot connect to Logseq" 1. Check Logseq is running with HTTP API enabled 2. Verify port: Default is 12315, check Settings → Advanced 3. Check firewall: Ensure localhost:12315 is accessible 4. Test manually: "Authentication failed" 1. Verify token: Check it matches what's in Logseq settings 2. Token format: Ensure no extra whitespace 3. Environment variable: Check echo $LOGSEQAPITOKEN "CLI not found" 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/connecting-to-logseq