Overview
What is Logseq MCP Tools?
Logseq MCP Tools is a Model Context Protocol (MCP) server that gives AI assistants like Claude structured access to your Logseq knowledge graph. It integrates with Logseq's HTTP API to retrieve pages, journal entries, backlinks, and perform graph analysis. Designed for Logseq users who want AI-powered exploration and summarization of their notes.
How to use Logseq MCP Tools?
Install via Smithery (npx -y @smithery/cli install @joelhooks/logseq-mcp-tools --client claude) or clone the repository, install dependencies, and configure your Logseq authentication token in a .env file. Start the server with npm start or npx tsx index.ts. Connect it to Claude Desktop, Cursor, the Anthropic API, or JetBrains Junie by adding the MCP configuration pointing to the built server.
Key features of Logseq MCP Tools
- Retrieve a list of all Logseq pages
- Get content and backlinks for any page
- Generate journal summaries for flexible date ranges
- Create and search pages in your graph
- Analyze knowledge graph structure and gaps
- Suggest connections between pages using AI
- Execute natural language queries via DataScript
Use cases of Logseq MCP Tools
- Ask an AI assistant to show your recent journal entries
- Summarize notes from last week or any time range
- Find all pages related to a specific topic
- Discover missing or underdeveloped pages in your graph
- Identify orphaned pages and potential connections
FAQ from Logseq MCP Tools
How do I get my Logseq authentication token?
Open Logseq, enable the HTTP API in Settings > Features, then set and copy your authentication token in Settings > Features > HTTP API Authentication Token. Place it in your .env file.
Does Logseq need to be running while using the server?
Yes, the MCP server communicates with Logseq via its HTTP API, so Logseq must be open and the HTTP API enabled.
What if Claude Desktop can't find Node.js?
Claude Desktop runs outside your shell environment. Install Node.js globally via Homebrew (brew install node) to ensure it is available to all applications.
How can I view logs for troubleshooting?
On macOS, monitor logs in real time with tail -n 20 -F ~/Library/Logs/Claude/mcp*.log. For detailed debugging, refer to the MCP debugging documentation.
What are the main dependencies?
The server is built using the Model Context Protocol TypeScript SDK, Zod for parameter validation, and the Logseq HTTP API for data access.
