Skip to main content
Glama
Sign In
loci-mcp

loci-mcp

by gked
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to loci-mcp

No user-submitted related servers found.

    Related Servers

    • Zettelkasten MCP Server

      DimitrisMendes
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other MCP-compatible clients to create, link, search, explore, and synthesize atomic notes in a bidirectional knowledge graph. Supports tags, note types, semantic link types, and dual Markdown/SQLite storage for AI-assisted knowledge management.
      -

    • Zettelkasten MCP Server

      Sven9685
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables creating, linking, tagging, searching and exploring atomic notes that form a networked knowledge graph, with bidirectional semantic link types and markdown files as the source of truth. Supports knowledge creation, exploration and synthesis through Claude and other MCP-compatible clients.
      -

    • Zettelkasten MCP Server

      MalgorzataMills51
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables creating, linking, searching, and synthesizing atomic notes stored as human-readable Markdown files with a rebuildable SQLite index, forming a navigable knowledge graph through typed semantic relationships, tags, and distinct note types. It lets Claude and other MCP-compatible clients capture fleeting ideas, explore linked notes across domains, and surface central, similar, or orphaned notes for further synthesis.
      -

    • Zettelkasten MCP Server

      jaoki824
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other MCP-compatible clients to create, link, tag, search, and update atomic notes stored as Markdown files, building a bidirectional knowledge graph with semantic relationships. Also supports exploring and synthesizing that graph through tools that surface linked, similar, central, and orphaned notes.
      -
    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

    A3.8/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (write/read/patch/delete/search on vault nodes, separate versioning, inbox, ontology, and asset tools). A few boundaries blur: search_vault vs find_nodes vs resolve_mentions all retrieve nodes, and define_type competes with write_meta(file="ontology-user") which is also described as the way to register a user type. Descriptions do help sort these out, but the registration overlap is a real source of misselection.

    Naming Consistency4/5

    Nearly everything is snake_case verb_noun (write_vault, read_meta, scan_inbox, define_relation, execute_inbox_file_batch). The only wrinkle is inconsistent retrieval verbs — query_*, find_*, search_vault, get_inbox_plan, list_vault, read_vault — so similar read operations don't share a prefix. Still very readable and predictable overall.

    Tool Count3/5

    39 tools is heavy for a single server and sits in the top band of the rubric. The domain is genuinely broad (vault CRUD, git-style history, ontology extension, assets, staged inbox, skills), so most tools earn their place, but several could be folded together (find_nodes/search_vault, define_type/write_meta).

    Completeness4/5

    Coverage is unusually thorough: full node lifecycle plus versioning/restore, filtered and keyword retrieval, graph queries, ontology/relation extension, asset registration, and a staged-inbox workflow. Minor gaps remain — search_vault only matches title and summary (no body full-text search), and there is no rename/move or delete operation for user-defined types/relations beyond overwriting ontology-user.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources