Skip to main content
Glama
alvinteh-git

logseq-mcp

by alvinteh-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to logseq-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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 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
    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 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation: page retrieval, page creation, block creation/update, journal fetching, search, and querying. The only potentially related tools are get_page, get_all_pages, and search_pages, but their purposes are clearly differentiated by exact-match retrieval, full listing, and search.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case, such as create_block, get_page, search_pages, and execute_query. The naming convention is uniform and predictable throughout the entire set.

    Tool Count5/5

    Eight tools is well-scoped for a Logseq MCP server, covering page management, block manipulation, search, and querying without unnecessary bloat. Each tool has a clear role in the surface.

    Completeness3/5

    The server covers creation and reading for pages and creation/update for blocks, but missing operations like page update/delete, block delete, or block retrieval create notable gaps. Agents can work around some of these via execute_query, but lifecycle coverage is incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources