Logseq MCP Tools

🚀 Logseq MCP Tool

This is a Model Context Protocol (MCP) server that enables AI assistants to access your Logseq knowledge graph in a structured manner.

🚀 Quick Start

This project creates an MCP server that allows AI assistants like Claude to interact with your Logseq knowledge base. It offers the following features:

• Retrieve a list of all pages
• Fetch the content of a specific page
• Generate diary summaries with flexible date ranges
• Extract linked pages and explore connections

📦 Installation

1. Clone this repository.
2. Install dependencies using npm, yarn, or pnpm:

# Using npm
npm install

# Using yarn
yarn install

# Using pnpm
pnpm install

3. Copy the environment variable template and configure your Logseq token:

cp .env.template .env
# Edit your Logseq authentication token in .env

📚 Documentation

Configuration

This project includes a .env.template file that you can copy and rename to .env.

You can find your authentication token in Logseq:

1. Open Logseq.
2. Enable the HTTP API in "Settings" > "Features".
3. Set your authentication token in "Settings" > "Features" > "HTTP API Authentication Token".

Usage

Run the MCP Server

The server can be started with the following commands:

# Using npm script
npm start

# Or directly using tsx
npx tsx index.ts

Configure in Claude Desktop

1. Open the preferences in Claude Desktop.
2. Add a new MCP tool:
   • Name: logseq-mcp
   • Executable Path: /Applications/Claude Desktop.app/Contents/Frameworks/node.js (macOS) or C:\Program Files\Claude Desktop\node.exe (Windows)
   • Arguments: --port 3000 (Adjust according to your server port)

🔧 Technical Details

The server is built using the following technologies:

• Model Context Protocol TypeScript SDK
• Zod for parameter validation
• Logseq HTTP API to access data

To add new tools, define additional server.tool() methods in index.ts.

❓ Frequently Asked Questions

Node.js Version Managers (fnm, nvm, etc.)

If you use a Node.js version manager like fnm or nvm, Claude Desktop won't be able to access the Node.js binary correctly because it runs outside the shell environment where the PATH is modified.

Solution: Install a system-wide Node.js using Homebrew:

brew install node

This ensures that all applications, including Claude Desktop, can access Node.js.

Basic Troubleshooting Steps

• Make sure the HTTP API is enabled in Logseq.
• Verify that the token in .env matches the one set in Logseq.
• Check if the path to the index.ts file in the configuration is correct.
• Try running npx tsx index.ts directly in the terminal to confirm it works.

View Logs in Claude Desktop

Monitor logs in real-time:

# macOS
tail -n 20 -F ~/Library/Logs/Claude/mcp*.log

For more detailed debugging information, refer to the official MCP debugging documentation.