Ergut MCP LogSeq Server

Provides an MCP interface to interact with LogSeq via its API for graphs, pages and content management.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-ergut_mcp-logseq-server": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "env": {
        "LOGSEQ_API_URL": "http://localhost:12315",
        "LOGSEQ_API_TOKEN": "<your_api_token_here>"
      }
    }
  }
}

This MCP server lets you interact with LogSeq through its API, exposing convenient tools to list graphs and pages, read content, search, and manage pages from an MCP client. It enables automation and integration by routing LogSeq actions through a standardized MCP interface.

How to use

You connect to this server from your MCP client and then call its tools to manage your LogSeq data. The server exposes endpoints to list graphs, list pages, read a page’s content, search across pages, and create, update, or delete pages. Use these tools to build workflows that summarize notes, pull project content, or update meeting records directly from your automation scripts.

How to install

Prerequisites: you need Node.js installed on your system and the MCP toolkit ready to run stdio servers. You will run a small configuration that tells the MCP runtime how to start the LogSeq MCP server.

Create a working directory for the MCP server configuration.
Add the MCP server configuration JSON to a file in that directory. The following example config should be saved as a file (for instance mcp_config.json):

{
  "mcp-logseq": {
    "command": "uvx",
    "args": [
      "mcp-logseq"
    ],
    "env": {
      "LOGSEQ_API_TOKEN": "<your_api_token_here>",
      "LOGSEQ_API_URL": "http://localhost:12315"
    }
  }
}

Additional configuration and notes

You can also place the required environment variables into a .env file in the working directory. The variables mirror the same values shown in the config snippet.

LOGSEQ_API_TOKEN=your_token_here
LOGSEQ_API_URL=http://localhost:12315

Available tools

list_graphs

Lists all available LogSeq graphs in the connected LogSeq instance.

list_pages

Lists all pages in the current graph.

get_page_content

Returns the content of a single page by its identifier.

search

Searches content across all pages in the graphs.

create_page

Creates a new page with specified title and content.

update_page

Updates the content of an existing page.

delete_page

Deletes a page by its identifier.