Ergut MCP Logseq Server

🚀 MCP Server for LogSeq

An MCP server for interacting with LogSeq via its API.

🚀 Quick Start

The MCP server for LogSeq enables seamless interaction with LogSeq through its API, offering a range of tools to manage pages and graphs efficiently.

✨ Features

Tools

The server implements several tools to interact with LogSeq:

• list_graphs: Lists all available graphs.
• list_pages: Lists all pages in the current graph.
• get_page_content: Returns the content of a single page.
• search: Searches for content across all pages.
• create_page: Creates a new page.
• update_page: Updates the content of an existing page.
• delete_page: Deletes a page.

Example Prompts

It's a good idea to first instruct Claude to use LogSeq. Then it will always call the tools.

Example prompts:

• Get the content of my latest meeting notes and summarize them.
• Search for all pages mentioning Project X and explain the context.
• Create a new page for today's meeting notes.
• Update the page with the latest status of the project.

📦 Installation

LogSeq API Configuration

You can configure the environment and LogSeq API settings in two ways:

1. Add to the server configuration (recommended)

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

2. Create a .env file in the working directory containing the required variables:

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

🔧 Technical Details

Building

When preparing the distribution package:

1. Synchronize dependencies and update the lock file:

uv sync

Debugging

Since the MCP server runs via stdio, debugging can be challenging. For the best debugging experience, we recommend using MCP Inspector.

You can start the MCP inspector via npm:

npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-logseq run mcp-logseq