Skip to main content
Glama
dailydaniel

Logseq MCP Server

by dailydaniel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Logseq MCP Server

No user-submitted related servers found.

    Related Servers

    • Logseq MCP Tools

      mikeysrecipes
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to interact with a local Logseq instance, allowing operations like creating pages, managing blocks, and searching across a knowledge graph.
      13
      1
      MIT

    • Logseq MCP Tools

      apw124
      A
      license
      A
      quality
      F
      maintenance
      A 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.
      13
      15
      MIT

    • logseq-mcp

      alvinteh-git
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with Logseq graphs, enabling AI assistants to read, create, and manipulate Logseq content.
      MIT

    • logseq-mcp

      anshulbansod2
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an AI agent operate a Logseq (DB) graph through safe, high-level tools for reading and managing notes, tasks, and projects without needing to know Logseq's internals.
      1
      MIT

    • Logseq MCP Server

      eugeneyvt
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      21
      7
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation3/5

    The tools have clear distinct purposes for core operations like creating pages, editing blocks, and retrieving content, but there is notable overlap between retrieval tools. Specifically, logseq_get_page and logseq_get_page_content both retrieve page details, and logseq_get_current_page_content and logseq_get_editing_block_content focus on current workspace content, which could cause confusion in selection. Descriptions help differentiate, but the boundaries are not perfectly distinct.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a 'logseq_' prefix, using clear verb_noun combinations such as create_page, edit_block, and get_all_pages. This uniformity makes the tools predictable and easy to parse, with no deviations in style or structure across the set.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a Logseq server, covering essential operations like page creation, editing, and content retrieval. Each tool serves a specific function without redundancy, fitting within the typical 3-15 range for such a domain, and no tools feel unnecessary or missing for basic interactions.

    Completeness4/5

    The tool set provides good coverage for core Logseq workflows, including CRUD-like operations for pages and blocks (create, get, edit, insert). However, there are minor gaps, such as no explicit tools for deleting pages or blocks, updating block content beyond editing mode, or managing properties post-creation, which agents might need to work around using existing tools.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources