Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"logseq": {
"args": [
"tsx",
"/path/to/your/index.ts"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that provides AI assistants with structured access to your Logseq knowledge graph.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@joelhooks/logseq-mcp-tools' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @joelhooks/logseq-mcp-tools against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Persistent memory using a knowledge graph
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
a self-hosted project management & Kanban solution + Instant shareable boards
All-in-one local AI hub for Obsidian — LLM chat with vault tools, MCP servers, RAG, workflow automation, encryption, and edit history. Fully private, no cloud required.
MCP Security Weekly
Get CVE alerts and security updates for Logseq Mcp Tools and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that provides AI assistants with structured access to your Logseq knowledge graph.
This project creates an MCP server that allows AI assistants like Claude to interact with your Logseq knowledge base. It provides tools for:
To install Logseq Tools for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @joelhooks/logseq-mcp-tools --client claude
# Using npm
npm install
# Using yarn
yarn install
# Using pnpm
pnpm install
cp .env.template .env
# Edit .env with your Logseq authentication token
This project includes a .env.template file that you can copy and rename to .env.
You can find your Logseq auth token by:
The server can be started using:
# Using the npm script
npm start
# Or directly with tsx
npx tsx index.ts
Follow the Claude MCP Quickstart guide:
brew install node
claude_desktop_config.json file. Replace its contents with:{
"mcpServers": {
"logseq": {
"command": "npx",
"args": [
"tsx",
"/path/to/your/index.ts"
]
}
}
}
IMPORTANT: Replace /path/to/your/index.ts with the exact absolute path to your index.ts file (e.g.,
/Users/username/Code/logseq-mcp-tools/index.ts)
Now you can chat with Claude and ask it to use your Logseq data:
Follow the Cursor MCP documentation:
npx tsx "/path/to/index.ts"
Now you can use Claude in Cursor with your Logseq data.
When using the Claude API or CLI tools, you can add the MCP service with:
claude mcp add "logseq" npx tsx "/path/to/index.ts"
To run this project with JetBrains Junie, follow these steps:
Build the Docker image:
docker build -t logseq-mcp .
# run in project root
Then add the following config to your Junie MCP configuration:
"logseq": {
"command": "c:\\Program Files\\Docker\\Docker\\resources\\bin\\docker.exe",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"-e",
"LOGSEQ_TOKEN=<Your Token>",
"-e",
"LOGSEQ_HOST=host.docker.internal",
"logseq-mcp"
]
}
Retrieves a list of all pages in your Logseq graph.
Gets the content of a specific page.
Parameters:
pageName: The name of the page to ret