Schema | mcp-pkm-logseq

mcp-pkm-logseq

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`LOGSEQ_URL`	No	URL where the Logseq HTTP API is running	http://localhost:12315
`LOGSEQ_API_KEY`	No	API key for authenticating with Logseq	this-is-my-logseq-mcp-token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
get_personal_notes_instructionsA	Get instructions on how to use the get_personal_notes tool. `This will return instructions on how the user organizes their personal notes in Logseq. It will contain common tags (topics), what they mean, and the workflows the user uses to organize their notes.`
get_personal_notesA	Retrieve personal notes from Logseq. Use this to find relavant information about a specific topic or about user preferences. It will return all information that is tagged with the topics from the user's personal knowledge base. The information is returned in markdown format, each item in the list is a separate unit of information. Hierachical information is returned as a nested list. The returning markdown contains text in double square brackets, like this: `[[topic]]`. These are links to other topics, you can follow them to get more information. Try variations of the topic to find the most relevant information. Dates are expressed as: 1. today\|yesterday\|tomorrow\|now 2. <number><unit> like 1d, 2w, 3m, 4y, 2h, 30min Args: topics: A list of topics to search for. Topics are case-insensitive. Topics are optional if there is a date range. from_date (optional): The start date to filter the notes. to_date (optional): The end date to filter the notes. Returns: A markdown formatted string containing the information with the given topics. Empty if no information is found.
get_todo_listA	Retrieve the todo list from Logseq. `Use this to get a list of all the todos in the user's personal knowledge base. Dates are expressed as: 1. today\|yesterday\|tomorrow\|now 2. <number><unit> like 1d, 2w, 3m, 4y, 2h, 30min Args: done: Whether to get the done todos or the todo todos. from_date (optional): The start date to filter the todos. to_date (optional): The end date to filter the todos. Returns: A markdown formatted string containing the todos.`

get_personal_notes_instructionsA

Get instructions on how to use the get_personal_notes tool.

This will return instructions on how the user organizes their personal notes in Logseq.

It will contain common tags (topics), what they mean, and the workflows the user
uses to organize their notes.

get_personal_notesA

Retrieve personal notes from Logseq.

Use this to find relavant information about a specific topic or about user preferences.
It will return all information that is tagged with the topics from the user's personal
knowledge base.

The information is returned in markdown format, each item in the list is a separate
unit of information. Hierachical information is returned as a nested list.

The returning markdown contains text in double square brackets, like this:
`[[topic]]`. These are links to other topics, you can follow them to get more
information. Try variations of the topic to find the most relevant information.

Dates are expressed as:
1. today|yesterday|tomorrow|now
2. <number><unit> like 1d, 2w, 3m, 4y, 2h, 30min

Args:
    topics: A list of topics to search for. Topics are case-insensitive. Topics
            are optional if there is a date range.
    from_date (optional): The start date to filter the notes.
    to_date (optional): The end date to filter the notes.

Returns:
    A markdown formatted string containing the information with the given topics.
    Empty if no information is found.

get_todo_listA

Retrieve the todo list from Logseq.

Use this to get a list of all the todos in the user's personal knowledge base.

Dates are expressed as:
1. today|yesterday|tomorrow|now
2. <number><unit> like 1d, 2w, 3m, 4y, 2h, 30min

Args:
    done: Whether to get the done todos or the todo todos.
    from_date (optional): The start date to filter the todos.
    to_date (optional): The end date to filter the todos.

Returns:
    A markdown formatted string containing the todos.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
`logseq://guide`

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored 2026-06-09 18:01 across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: retrieving notes, retrieving instructions for notes retrieval, and retrieving todos. No overlap or ambiguity between them.

Naming Consistency5/5

All tools follow the consistent 'get_' prefix and a descriptive noun pattern (get_personal_notes, get_personal_notes_instructions, get_todo_list). No naming style mixing.

Tool Count4/5

With only 3 tools, the server is minimal but appropriate for a read-only retrieval interface over a personal knowledge base. Slightly scoped down but not underdeveloped for its purpose.

Completeness3/5

Covers retrieval of notes and todos, but lacks any creation, update, or deletion capabilities. While the server may be intentionally read-only, obvious lifecycle operations are missing, limiting agent workflows.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers