What environment variables does mcp-pkm-logseq require?
`LOGSEQ_API_KEY` (default: `"this-is-my-logseq-mcp-token"`) for authentication and `LOGSEQ_URL` (default: `"http://localhost:12315"`) for the Logseq HTTP API endpoint.
@ruliana
Basic information
A fairly customizable MCP server for Logseq
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-pkm-logseq": {
"command": "uv",
"args": [
"sync"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
mcp-pkm-logseq is an MCP server that enables AI assistants to interact with your Logseq Personal Knowledge Management system. It provides tools to retrieve notes and todos from your Logseq graph, guided by a custom instructions page you create. It is intended for users who want LLM-powered access to their Logseq knowledge base.
Install via uvx mcp-pkm-logseq and configure the environment variables LOGSEQ_API_KEY (default "this-is-my-logseq-mcp-token") and LOGSEQ_URL (default "http://localhost:12315"). Enable Logseq’s built-in HTTP API server in Settings → Advanced → Developer mode, set your API token, then configure your MCP client (e.g., Claude Desktop, Claude Code, Cursor) with the server command and environment variables. A page named “MCP PKM Logseq” should be created in your graph to serve as an AI guide.
logseq://guide) for assistant instructions.`LOGSEQ_API_KEY` (default: `"this-is-my-logseq-mcp-token"`) for authentication and `LOGSEQ_URL` (default: `"http://localhost:12315"`) for the Logseq HTTP API endpoint.
Open Logseq, go to Settings → Advanced, enable “Developer mode” and “HTTP API Server”, then set your API token to match the `LOGSEQ_API_KEY` value.
On macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`; on Windows: `%APPDATA%/Claude/claude_desktop_config.json`. Add the server under `mcpServers` with `"command": "uvx"` and `"args": ["mcp-pkm-logseq"]`.
It is a guide page you create in your Logseq graph containing your tagging system, workflows, naming conventions, and search preferences. The server exposes it as a resource so the AI assistant can understand how to interact with your knowledge base.
Use the MCP Inspector by running `npx @modelcontextprotocol/inspector uv --directory <path> run mcp-pkm-logseq`. This provides a browser-based debugging interface.
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 162 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

One permissioned folder your team and your AI agents both log into.

Search saved employee handbooks from your AI assistant. Four read-only tools list authorized handbooks, browse policies, search content, and read source pages with citation links. Uses scoped bearer tokens and Streamable
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.
Project context your AI can query through MCP — with source evidence.
Comments