Skip to main content
Glama
sharedlore-ai

Lore MCP

Official
by sharedlore-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Lore MCP

No user-submitted related servers found.

    Related Servers

    • mcp-agent-bridge

      xfajarr
      A
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server that provides shared, real-time context across multiple AI agents via WebSocket and MCP resource notifications, enabling collaborative workspaces, memory, tasks, and messaging.
      14 npm
      2
      MIT

    • mnemon-mcp

      nikitacometa
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.
      84 npm
      3
      MIT

    • HYTHE

      hythe-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets multiple AI coding agents share state, preserve context across sessions, and coordinate via a knowledge graph, messaging, and branch-preserving checkpoint/resume with conflict handling.
      42 npm
      Apache 2.0

    • mulchd

      ChacheGS
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP server for storing and serving structured team knowledge, enabling AI sessions to load relevant team context without re-prompting.
      Apache 2.0

    • knitbrain

      PDgit12
      A
      license
      A
      quality
      C
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      26 npm
      6
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct node kind or action (create/update for specific types, delete, move, search, list). Even lore_context combines read and write but is clearly described based on body presence. No two tools serve the same purpose.

    Naming Consistency4/5

    All tools share the 'lore_' prefix. Most use a single noun or verb (adr, capture, context, delete, log, memory, move, plan, search, start, todo, tree) but some are two-word verbs (create_project) and a few are nouns used as verbs (adr, context, log, memory, plan, todo, tree). The pattern is consistent across the set but not perfectly verb_noun.

    Tool Count5/5

    With 14 tools covering node lifecycle (create/update for 6 types, delete, move, search, list, projects, startup briefing), the count is well-scoped for a knowledge management server. Each tool serves a clear purpose without being excessive.

    Completeness4/5

    Core CRUD is covered for all node types via create/update, delete, and move. Search and tree listing provide access. Minor gaps include no dedicated 'get single node by path' tool for all types, but search and context fetch cover retrieval. Overall surface is sufficient for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources