Skip to main content
Glama
emiliano-go

totem-mcp

by emiliano-go
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to totem-mcp

No user-submitted related servers found.

    Related Servers

    • Argon Memory

      Tangtaizong-BUAA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.
      1
      Apache 2.0

    • arcane

      Edition-X
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.
      MIT

    • Memory MCP

      EtienneBBeaulac
      A
      license
      A
      quality
      C
      maintenance
      Gives AI coding agents persistent, evolving knowledge about a codebase, enabling them to store and retrieve observations about architecture, conventions, gotchas, and recent work context.
      10
      5 npm
      3
      MIT

    • Memory Cortex

      TYRANNOSAURX
      A
      license
      Not graded
      quality
      C
      maintenance
      Durable, inspectable memory for MCP agents. Preserves decisions, preferences, and project knowledge across sessions with full provenance and version history.
      3
      Apache 2.0

    • almanac

      AndriGitDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to capture, search, and recall persistent knowledge notes with epistemic metadata, automatically injecting relevant context into their sessions.
      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

    C2.5/5.0

    Scored across 31 tools

    Disambiguation2/5

    The set includes 14 type-specific create tools plus a generic memory_create_tool with a type argument, so agents must decide between a specialized wrapper and the generic path for the same action. flag_ambiguity is an explicit duplicate of ambiguity_create, and register_file_read_tool overlaps with implementation_create for storing code facts.

    Naming Consistency2/5

    Naming is split across at least three patterns: noun_verb create tools without a suffix (gotcha_create, decision_create), memory_*_tool functions with a suffix (memory_get_tool, memory_list_tool), and one-off names like flag_ambiguity and engineering_context_tool. The inconsistent ordering and suffix usage make the tool names hard to predict.

    Tool Count2/5

    At 31 tools, the server is overbuilt for its purpose, largely because the 14 type-specific create wrappers duplicate the functionality of memory_create_tool. A leaner set of around 15-18 tools would cover the same memory lifecycle without the redundancy.

    Completeness4/5

    The memory lifecycle is well covered with create, update, get, delete, list, search, import/export, init, file-write registration, and conflict resolution. The main gap is the lack of a dedicated conflict-list/get tool; conflicts are only surfaced indirectly through export or engineering context.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources