/ Каталог / Песочница / mcp-logseq
● Сообщество ergut ⚡ Сразу

mcp-logseq

автор ergut · ergut/mcp-logseq

Make your Logseq graph AI-queryable — read pages, create blocks, search by property, run DSL queries — over Logseq's local HTTP API.

mcp-logseq by ergut connects an MCP client to Logseq's Local HTTP API. 16 core tools cover pages, blocks, namespaces, backlinks, and DSL queries. Optional vector search adds semantic recall across the whole graph.

Зачем использовать

Ключевые функции

Живое демо

Как выглядит на практике

logseq.replay ▶ готово
0/0

Установка

Выберите клиент

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "logseq",
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json
{
  "context_servers": {
    "logseq": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-logseq"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add logseq -- uvx mcp-logseq

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: mcp-logseq

Draft today's daily journal from your week

👤 Logseq power users ⏱ ~10 min beginner

Когда использовать: Friday reflection; you want a summary of the week's journal pages.

Предварительные требования
  • Logseq with HTTP API enabled — Settings > Features > enable HTTP APIs; generate API token
  • LOGSEQ_API_TOKEN + LOGSEQ_API_URL env vars — Set in your MCP client config
Поток
  1. Pull last week's journal pages
    Get the content of this week's daily journal pages (Monday through today).✓ Скопировано
    → Page contents per day
  2. Summarize and draft
    Summarize themes and draft today's journal with a Week Review section.✓ Скопировано
    → Draft ready to paste
  3. Write back
    Update today's journal page, appending the Week Review section.✓ Скопировано
    → Page updated

Итог: A closing-the-loop weekly reflection with minimal typing.

Подводные камни
  • update_page in append mode duplicates content on retry — Use replace mode for idempotent operations, or check existing content first
  • Sensitive tags leak into summaries — Set LOGSEQ_EXCLUDE_TAGS=private,#secret to hide those

Find pages by property for a task sweep

👤 Logseq users with task-style pages ⏱ ~15 min beginner

Когда использовать: You tag project pages with status:: active and want a list.

Поток
  1. Find by property
    find_pages_by_property: status=active. Return names and updated-at.✓ Скопировано
    → Page list
  2. Triage
    For each, fetch the page and tell me the last 3 blocks — is there a visible next action?✓ Скопировано
    → Per-page status

Итог: A sweep of active projects with clear next actions.

Semantic recall across your whole graph

👤 Researchers with a huge Logseq graph ⏱ ~10 min intermediate

Когда использовать: Keyword search isn't finding a note you know you wrote.

Предварительные требования
  • Vector DB synced — Run sync_vector_db once; re-run after big imports
Поток
  1. Vector search
    vector_search: 'what did I note about test pyramid vs honeycomb?'✓ Скопировано
    → Ranked matches
  2. Pull full page
    get_page_content on the top match.✓ Скопировано
    → Full content

Итог: Finding notes by meaning, not exact words.

Turn a meeting page into tracked action items

👤 PMs and team leads ⏱ ~10 min beginner

Когда использовать: You capture meetings in Logseq and want the actions separated.

Поток
  1. Read meeting page
    get_page_content for 'Meeting/2026-04-14/engineering-sync'.✓ Скопировано
    → Notes
  2. Extract actions
    Identify TODO-flavored lines. For each, create a child block under today's journal with assignee and due date.✓ Скопировано
    → Blocks created

Итог: Actions lifted out of notes into a trackable list.

Комбинации

Сочетайте с другими MCP — эффект x10

logseq + marm-systems

Short-lived recall in MARM; durable notes in Logseq

Move these MARM contextual logs into Logseq as pages under /Notes/2026-04.✓ Скопировано
logseq + filesystem

Export curated Logseq pages to Markdown files

Export all pages tagged #public to ./exports/public-notes/ as individual .md files.✓ Скопировано

Инструменты

Что предоставляет этот MCP

ИнструментВходные данныеКогда вызыватьСтоимость
list_pages (none) Graph overview free (local API)
get_page_content name: str Read a page free
create_page name, content, properties? New page free (write)
update_page name, content, mode: append|replace Edit an existing page free (write)
delete_page name: str Destructive — confirm free
search query: str Full-text search free
query dsl: str Logseq DSL query free
find_pages_by_property key: str, value?: str Filter by properties free
get_page_backlinks name: str Who links to this note free
insert_nested_block parent_uuid, content, position: child|sibling Add structured content free (write)
vector_search query: str Semantic recall free (local embeddings)

Стоимость и лимиты

Во что обходится

Квота API
None — Logseq's local API is unbounded
Токенов на вызов
Small for list/search; pages can be long
Деньги
Free
Совет
For graphs with 10k+ pages, keep vector DB synced nightly rather than on every query.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: LOGSEQ_API_TOKEN in env var
Исходящий трафик: All local to Logseq; vector embeddings stay on your machine
Никогда не давайте: Exposing Logseq's HTTP API to your LAN without firewalling

Устранение неполадок

Частые ошибки и исправления

Connection refused on localhost:12315

Start the HTTP API via the plug icon in Logseq. It's off by default.

Проверить: curl http://localhost:12315
401 on API calls

Token missing or mismatched. Regenerate in Logseq Authorization tokens.

Проверить: Check token in Logseq settings
vector_search empty

Run sync_vector_db first; it's not auto-synced.

Проверить: vector_db_status

Альтернативы

mcp-logseq в сравнении

АльтернативаКогда использоватьКомпромисс
Obsidian MCP (community)You use Obsidian insteadDifferent graph semantics
Notion MCPYou're on NotionPaid SaaS; different graph model
filesystem MCP on the Logseq dirYou only need raw file accessNo block-level operations, no DSL queries

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills