Skip to main content
Glama
apw124

Logseq MCP Tools

by apw124
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Logseq MCP Tools

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

      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

    • personal-mcp-context

      januarsyah901
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that stores personal context as structured Markdown files with a knowledge graph, enabling AI agents to query identity, devices, servers, and projects on-demand.
      -

    • 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
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinct purpose targeting specific resources and actions in the Logseq graph. For example, create_block vs. insert_block clearly differentiate between creating a top-level block and inserting a child block, while get_page_blocks and search_blocks serve different retrieval functions. No tools appear to overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming (e.g., create_block, get_page, update_block). The verbs are clear and appropriate (create, get, delete, search, update, move, remove, insert), and the nouns consistently refer to Logseq entities (block, page). There are no deviations in naming conventions.

    Tool Count5/5

    With 13 tools, this server is well-scoped for managing a Logseq graph, covering core operations without bloat. The count aligns with the domain's complexity, providing comprehensive functionality for pages and blocks (e.g., CRUD operations, hierarchical management, search) without being excessive or insufficient.

    Completeness5/5

    The tool set offers complete coverage for Logseq graph management, including full CRUD for pages and blocks, hierarchical operations (insert_block, move_block), search capabilities, and reference tracking. There are no obvious gaps; agents can perform all essential workflows from creation to deletion with support for linking and properties.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources