mcp-logseq MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

16 tools for pages, blocks, namespaces, and Logseq DSL queries
Optional semantic vector search (vector_search, sync_vector_db)
Markdown-aware — create_page and update_page handle Logseq block formatting
DB-mode property support via LOGSEQ_DB_MODE
Tag exclusion filter (LOGSEQ_EXCLUDE_TAGS) to hide private pages from AI

Démo en direct

Aperçu en pratique

logseq.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "logseq": {
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "logseq",
      "command": "uvx",
      "args": [
        "mcp-logseq"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "logseq": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-logseq"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add logseq -- uvx mcp-logseq

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : mcp-logseq

Draft today's daily journal from your week

👤 Logseq power users ⏱ ~10 min beginner

Quand l'utiliser : Friday reflection; you want a summary of the week's journal pages.

Prérequis

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

Déroulement

Pull last week's journal pages

Get the content of this week's daily journal pages (Monday through today).✓ Copié

→ Page contents per day
Summarize and draft

Summarize themes and draft today's journal with a Week Review section.✓ Copié

→ Draft ready to paste
Write back

Update today's journal page, appending the Week Review section.✓ Copié

→ Page updated

Résultat : A closing-the-loop weekly reflection with minimal typing.

Pièges

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

Quand l'utiliser : You tag project pages with status:: active and want a list.

Déroulement

Find by property

find_pages_by_property: status=active. Return names and updated-at.✓ Copié

→ Page list
Triage

For each, fetch the page and tell me the last 3 blocks — is there a visible next action?✓ Copié

→ Per-page status

Résultat : A sweep of active projects with clear next actions.

Semantic recall across your whole graph

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

Quand l'utiliser : Keyword search isn't finding a note you know you wrote.

Prérequis

Vector DB synced — Run sync_vector_db once; re-run after big imports

Déroulement

Vector search

vector_search: 'what did I note about test pyramid vs honeycomb?'✓ Copié

→ Ranked matches
Pull full page

get_page_content on the top match.✓ Copié

→ Full content

Résultat : Finding notes by meaning, not exact words.

Turn a meeting page into tracked action items

👤 PMs and team leads ⏱ ~10 min beginner

Quand l'utiliser : You capture meetings in Logseq and want the actions separated.

Déroulement

Read meeting page

get_page_content for 'Meeting/2026-04-14/engineering-sync'.✓ Copié

→ Notes
Extract actions

Identify TODO-flavored lines. For each, create a child block under today's journal with assignee and due date.✓ Copié

→ Blocks created

Résultat : Actions lifted out of notes into a trackable list.

Combinaisons

Associez-le à d'autres MCPs pour un effet 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.✓ Copié

logseq + filesystem

Export curated Logseq pages to Markdown files

Export all pages tagged #public to ./exports/public-notes/ as individual .md files.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
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)

Coût et limites

Coût d'exécution

Quota d'API: None — Logseq's local API is unbounded
Tokens par appel: Small for list/search; pages can be long
Monétaire: Free
Astuce: For graphs with 10k+ pages, keep vector DB synced nightly rather than on every query.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : LOGSEQ_API_TOKEN in env var

Sortie de données : All local to Logseq; vector embeddings stay on your machine

Ne jamais accorder : Exposing Logseq's HTTP API to your LAN without firewalling

Logseq's HTTP API has full graph write access — protect the token as a secret.
Use LOGSEQ_EXCLUDE_TAGS to redact private pages from AI visibility.

Dépannage

Erreurs courantes et correctifs

Connection refused on localhost:12315

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

Vérifier : curl http://localhost:12315

401 on API calls

Token missing or mismatched. Regenerate in Logseq Authorization tokens.

Vérifier : Check token in Logseq settings

vector_search empty

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

Vérifier : vector_db_status

Alternatives

mcp-logseq vs autres

Alternative	Quand l'utiliser	Compromis
Obsidian MCP (community)	You use Obsidian instead	Different graph semantics
Notion MCP	You're on Notion	Paid SaaS; different graph model
filesystem MCP on the Logseq dir	You only need raw file access	No block-level operations, no DSL queries

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills