The MCP server for LogSeq enables Claude to programmatically interact with LogSeq graphs via its API, providing comprehensive knowledge management and automation capabilities.
Core Functions:
Create Pages: Generate new pages by specifying title and content
List Pages: Retrieve all pages in your graph, with optional inclusion of journal/daily notes
Read Page Content: Access and read content from specific pages
Update Pages: Modify existing page content
Delete Pages: Remove unwanted pages from your graph
Search Content: Find specific content across your entire LogSeq graph
AI-Powered Workflows: Automate tasks like summarizing notes, organizing content, and generating new pages based on existing data for enhanced knowledge management.
Allows interaction with LogSeq via its API, including listing graphs and pages, getting, creating, updating, and deleting pages, and searching content across all pages
MCP server for LogSeq
MCP server to interact with LogSeq via its API.
Components
Tools
The server implements multiple tools to interact with LogSeq:
list_graphs: Lists all available graphs
list_pages: Lists all pages in the current graph
get_page_content: Return the content of a single page
search: Search for content across all pages
create_page: Create a new page
update_page: Update content of an existing page
delete_page: Delete a page
Example prompts
It's good to first instruct Claude to use LogSeq. Then it will always call the tool.
Example prompts:
Get the contents of my latest meeting notes and summarize them
Search for all pages where Project X is mentioned and explain the context
Create a new page with today's meeting notes
Update the project status page with the latest updates
Configuration
LogSeq API Configuration
You can configure the environment with LogSeq API settings in two ways:
Add to server config (preferred)
Create a
.env
file in the working directory with the required variables:
Development
Building
To prepare the package for distribution:
Sync dependencies and update lockfile:
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we recommend using the MCP Inspector.
You can launch the MCP Inspector via npm
with:
local-only server
The server can only run on the client's local machine because it depends on local resources.
Interacts with LogSeq via its API.
Related MCP Servers
- AsecurityAlicenseAqualityA server that enables LLMs to programmatically interact with Logseq knowledge graphs, allowing creation and management of pages and blocks.Last updated -1024MIT License
- -securityFlicense-qualityEnables querying log data stored in SQLite databases through the Model Context Protocol, allowing natural language interactions with log analysis.Last updated -
- -securityFlicense-qualityA Model Context Protocol server that provides AI assistants with structured access to your Logseq knowledge graph, enabling retrieval, searching, analysis, and creation of content within your personal knowledge base.Last updated -50
- AsecurityAlicenseAqualityEnables interaction with Datadog's monitoring platform to search logs, search trace spans, and perform trace span aggregation for analysis.Last updated -3MIT License