MCP server to interact with LogSeq via its Local HTTP API - enabling AI assistants like Claude to seamlessly read, wr...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Universal
Model
Claude
Fastest way to find out if mcp-logseq belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add mcp-logseq -- npx mcp-logseqRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove mcp-logseqNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ mcp-logseq ← registers here
MCP server to interact with LogSeq via its Local HTTP API - enabling AI assistants like Claude to seamlessly read, write, and manage your LogSeq graph.