Logseq MCP Tools MCP Server

MCP Server for interacting with LogSeq graph

Local serverstdioPython

What is the Logseq MCP Tools MCP server?

Connect Logseq MCP Tools to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server for interacting with LogSeq graph. The logseq mcp tools mcp server is what makes that connection.

What the server does

This project provides a set of Model Context Protocol (MCP) tools that enable AI agents to interact with your local Logseq instance.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Pages — The Pages tool exposed by this server
  • Blocks — The Blocks tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: LOGSEQ_API_URL, LOGSEQ_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at logseq-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Logseq MCP Tools's toolset — Pages, Blocks — is a fair guide to whether it matches your workflow. It is maintained by apw124; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Logseq MCP Tools's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
PagesThe Pages tool exposed by this server.
BlocksThe Blocks tool exposed by this server.

How to install the Logseq MCP Tools MCP server

{
  "mcpServers": {
    "logseq-mcp-apw124": {
      "command": "uvx",
      "args": ["logseq-mcp"],
      "env": {
        "LOGSEQ_API_URL": "your-value",
        "LOGSEQ_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LOGSEQ_API_URLEndpoint or connection string the server talks to.Yes
LOGSEQ_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Logseq MCP Tools to Pages.
  • Use Logseq MCP Tools to Blocks.

Frequently asked questions

Python 3.11+ and a local Logseq instance with Developer mode enabled, Developer Plugin turned on, and an API token set in Advanced settings.