Skip to main content
Glama
davidgut1982

lore-mcp

by davidgut1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to lore-mcp

No user-submitted related servers found.

    Related Servers

    • trailmem

      amitnexTech
      A
      license
      A
      quality
      A
      maintenance
      Persistent, local-first graph memory for AI coding agents. Provides durable cross-session memory via a local SQLite knowledge graph with typed relationships.
      6
      1
      MIT

    • Open Brain Knowledge MCP

      melvenac
      F
      license
      A
      quality
      D
      maintenance
      A persistent, cross-session knowledge base for AI agents that indexes session history into a searchable SQLite database with full-text search, enabling recall of past sessions, stored knowledge, and summaries.
      10
      -

    • remembrallmcp

      roboticforce
      A
      license
      Not graded
      quality
      A
      maintenance
      Persistent knowledge memory layer for AI agents. Hybrid semantic + full-text search with pgvector, code dependency graph with blast-radius impact analysis, and incremental indexing for 7 languages. In-process ONNX embeddings, no external API required.
      38 npm
      35
      MIT

    • code-recall

      AbianS
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
      4
      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

    C2.7/5.0

    Scored across 42 tools

    Disambiguation3/5

    Most tools are cleanly separated by domain prefixes and detailed descriptions, but mcp_index_scan and mcp_index_rebuild are effectively the same operation, and the many search-related tools (kb_search, search_local, search_corpora, search_transcripts, multi_search) require careful reading to avoid mis-selection.

    Naming Consistency4/5

    The naming is largely consistent: snake_case verb_noun patterns with domain prefixes like kb_, investigation_, journal_, and mcp_index_. Minor inconsistencies exist, such as mcp_index_scan/mcp_index_rebuild being duplicate operations and backfill_query_embeddings not following the kb_backfill_embeddings prefix style, but the overall pattern is predictable.

    Tool Count2/5

    42 tools is far too many for a single MCP server, even one spanning knowledge bases, investigations, journals, search, telemetry, and MCP indexing. The surface would be more usable split into smaller focused servers or consolidated into fewer higher-level tools.

    Completeness4/5

    The knowledge base has full CRUD plus ingestion and embedding workflows; investigations, journals, search, telemetry, and MCP indexing all cover their core lifecycles. Minor gaps like no explicit investigation or journal update operation are likely intentional given the append-oriented design, but they are still notable omissions.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources