Skip to main content
Glama
dearcloud09

Logseq MCP Server

by dearcloud09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Logseq MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      10 npm
      7
      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.
      10 npm
      Apache 2.0

    • 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

      joseguzmann
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to read Logseq notes, journals, tasks, pages and blocks—including embedded screenshots as viewable images—directly from the on-disk graph. It works read-only with Logseq closed and no network access, snapshotting the database so nothing can be modified.
      8
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the Logseq domain, such as create_page vs. read_page vs. update_page vs. delete_page for page lifecycle, and get_backlinks vs. get_graph vs. search_pages for different query types. No tools appear to overlap or cause confusion in selection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as append_to_page, create_journal, and get_backlinks. This predictable naming scheme makes it easy for an agent to understand and use the tools without ambiguity or style mixing.

    Tool Count5/5

    With 11 tools, the server is well-scoped for managing a knowledge graph like Logseq, covering essential operations from CRUD for pages and journals to advanced queries like backlinks and graph data. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete coverage for the Logseq domain, including full CRUD lifecycle for pages and journals, listing, reading, updating, deleting, and specialized operations like backlinks, graph retrieval, and search. There are no obvious gaps that would hinder agent workflows in this context.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources