mcp-pkm-logseq
Related Servers
Alternatives to mcp-pkm-logseq
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects MCP-compatible AI assistants to Logseq graphs, enabling block-first operations, block references, and context graph building.MIT
- AlicenseAqualityAmaintenanceInteracts with LogSeq via its API.17698 PyPI340MIT
- AlicenseCqualityDmaintenancePython stdio MCP server that interfaces with the Logseq local HTTP API, enabling tools to manage pages, blocks, queries, and graph configurations in Logseq.642MIT
- AlicenseAqualityDmaintenanceAn MCP server for interacting with Logseq graphs, enabling AI assistants to read, create, and manipulate Logseq content.8MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol server that enables AI agents to interact with local Logseq knowledge graphs, supporting operations like creating/editing pages and blocks, searching content, and managing journal entries.1315MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with your local Logseq knowledge base through advanced search, content creation, template management, and knowledge organization with privacy-first, local-only operations.24 npm7MIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: retrieving notes, retrieving instructions for notes retrieval, and retrieving todos. No overlap or ambiguity between them.
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.
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.
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.