Skip to main content
Glama
ergut

MCP server for LogSeq

by ergut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP server for LogSeq

No user-submitted related servers found.

    Related Servers

    • mcp-pkm-logseq

      ruliana
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with your Logseq personal knowledge management system via MCP, allowing retrieval of tagged notes and todo lists through Logseq's HTTP API.
      3
      9
      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.
      7 npm
      7
      MIT

    • MCP-Logseq

      varunity
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects MCP-compatible AI assistants to Logseq graphs, enabling block-first operations, block references, and context graph building.
      MIT

    • Logseq MCP Server

      dearcloud09
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants like Claude to directly read, write, search, and navigate your local Logseq knowledge graph, including managing journals, pages, backlinks, and page relationships without manual copy-pasting.
      11
      3 npm
      6
      MIT

    • Logseq MCP Server

      hsiang119
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Logseq knowledge graphs to read, write, and search pages, blocks, and journals via the Model Context Protocol. It features 17 tools for full graph management, including CRUD operations, batch block insertion, and full-text search.
      7 npm
      Apache 2.0
    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

    A3.5/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool targets a clear resource (page vs block) and action, but search/query/find_pages_by_property and the two namespace getters have overlapping purposes that could cause an agent to pick the wrong one.

    Naming Consistency4/5

    Most tools follow verb_noun (list_pages, create_page, get_block, delete_block), but 'search' and 'query' break the pattern as bare verbs, and set_block_properties could be seen as an update_block variant.

    Tool Count4/5

    17 tools is slightly above the ideal 3-15 range, but the set covers pages, blocks, search, queries, namespaces, backlinks, and properties without obvious redundancy.

    Completeness4/5

    The surface provides full page and block CRUD plus search/query, namespaces, backlinks, and properties. Missing standalone root block creation and journal-specific tools, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources