Skip to main content
Glama
lasheralberto

obsidian-local-mcp

by lasheralberto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to obsidian-local-mcp

No user-submitted related servers found.

    Related Servers

    • engram-serve

      kortiz72879
      A
      license
      Not graded
      quality
      A
      maintenance
      Serves focused, token-bounded context from a project-local SQLite structural code graph to AI coding agents, exposing indexed entities, Git relationships and recorded project memory for exploration, impact analysis and session continuity. Runs locally with a CLI, hooks, authenticated dashboard and optional plugin providers.
      6 npm
      MIT

    • Threadnote

      threadnote
      A
      license
      B
      quality
      A
      maintenance
      Local-first engineering memory and code-graph tools for coding agents. Supports private session handoffs, code-cited knowledge, repository graph inspection, and optional Git-backed team sharing.
      25
      11 npm
      26
      AGPL 3.0

    • Engram

      dimitriou28217
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a locally indexed structural code graph — source entities, callers/callees, Git relationships and recorded mistakes — so they retrieve focused, token-bounded context instead of reading entire files. It runs over local SQLite and can be served through a CLI, agent hooks, an MCP executable and an authenticated local dashboard.
      6 npm
      MIT

    • NervaPack

      ramdhavepreetam
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to retrieve hyper-targeted, token-efficient context from a codebase by querying a locally built AST knowledge graph, and to persist cross-session agent memory through 17 MCP tools. All indexing and retrieval run entirely offline, so proprietary code never leaves the machine.
      80 PyPI
      1
      MIT

    • engram-serve

      Stefanie82399
      A
      license
      Not graded
      quality
      A
      maintenance
      Serves AI coding agents focused context from a project-local SQLite graph of source entities and Git relationships, so they can retrieve relevant code, trace callers/callees and impact, and carry recorded mistakes into later sessions without reading whole files. Queries render bounded, token-estimated packets while all indexing stays on the local machine.
      6 npm
      MIT

    • braindump

      mmkumar5401
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to persist and retrieve notes, code entities, and typed links in a local graph database across sessions, with hybrid offline search, graph traversal, and staleness checks. It also supports export/import and CLI access for backup and transfer.
      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.1/5.0

    Scored across 30 tools

    Disambiguation4/5

    The set is mostly well-differentiated, with clear splits between node/edge CRUD, note operations, indexing, and context queries. Minor overlaps remain, especially between search_vault and search_nodes, and between consolidation_report and detect_divergence, but descriptions usually clarify the intended choice.

    Naming Consistency4/5

    All tool names use snake_case consistently, and most follow recognizable verb_noun or verb_object patterns. A few tools are noun-only or prepositional phrases (neighbors, graph_stats, path_between, impact_of), which is a minor deviation from a strict verb_noun convention.

    Tool Count2/5

    With 30 tools, the surface is above the 25+ threshold that typically indicates an overloaded set. The domain is complex, but the many granular single/batch and lifecycle operations could likely be consolidated or grouped more tightly.

    Completeness4/5

    The set covers node/edge lifecycle, note lifecycle, indexing, retrieval, impact analysis, pathfinding, stats, divergence detection, and consolidation. Gaps are minor: no batch delete, no explicit edge listing/search, no note rename, and no wikilink removal beyond additive sync.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources