Skip to main content
Glama
mohdaman892

eng-server

by mohdaman892
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to eng-server

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

    • Memory MCP

      nerdyaustin
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      MIT

    • coding-memory-mcp

      ChinaCarlos
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.
      36 npm
      2
      MIT

    • Simple Rick

      good-v1be
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with persistent memory by recording sessions and normalizing them into a searchable knowledge graph, then delivering relevant context at the start of the next session.
      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

    A3.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools divide into distinct workflow stages (session start, prepare, commit placements, commit step, search, conflicts), and descriptions explicitly clarify which call stores versus stages data. Some overlap exists between ecg_commit_placements and ecg_commit_step, and between ecg_cancel_step/ecg_discard_proposal, which could confuse ordering, but the descriptions distinguish them.

    Naming Consistency4/5

    All tools use a consistent ecg_ prefix followed by verb_noun snake_case (ecg_prepare_placements, ecg_commit_step, etc.). A few names like ecg_stats and ecg_search_context are noun/short forms, but the convention is otherwise predictable.

    Tool Count5/5

    12 tools is well within a healthy range and each maps to a distinct step in the memory workflow. The set is neither thin nor bloated for the stated purpose.

    Completeness5/5

    The surface covers the full lifecycle: session init, preparation, staging, provenance, consent, commit, cancellation, search, conflict listing/resolution, and stats. No obvious CRUD or lifecycle gaps remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources