Skip to main content
Glama
Johnsonxd4

mcp-logseq

by Johnsonxd4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-logseq

No user-submitted related servers found.

    Related Servers

    • logseq-mcp

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

      seojeom-mcpofficial

      seojeom
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first MCP server that binds to a project opened by the Seojeom desktop app and serves its local wiki and graph data over stdio, enabling project-aware reading, searching, and writing of wiki and graph content.
      6 npm
      MIT

    • mindgap

      grburgess
      A
      license
      A
      quality
      B
      maintenance
      Exposes the mindgap knowledge graph as an MCP server over stdio, providing tools to add, link, query, and manage nodes and edges in a local org-roam-style graph.
      10
      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 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

    • Personal OS MCP

      likalg
      F
      license
      A
      quality
      B
      maintenance
      MCP server for Personal OS API that enables managing tasks, notes, projects, collections, reviews, and more through typed tools over stdio.
      66
      -
    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

    C2.9/5.0

    Scored across 64 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap between query/search/datascript_query and get_block_properties/get_block_property, which could cause misselection. Overall, descriptions help differentiate.

    Naming Consistency4/5

    The naming convention is largely consistent with verb_noun snake_case (e.g., get_block, create_page). However, a few outliers like check_current_is_db_graph, git_exec, and logseq_call deviate from the pattern, causing minor inconsistency.

    Tool Count2/5

    The 64 tools are excessive for typical MCP servers (usually 3-15). While Logseq has many features, this number may overwhelm agents, leading to poor selection and increased complexity.

    Completeness5/5

    The tool set covers nearly all aspects of Logseq: blocks, pages, tags, properties, graphs, configs, Git, assets, queries. There are no obvious gaps; users can perform full CRUD and lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources