Skip to main content
Glama
wallter

trw-mcp

by wallter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to trw-mcp

No user-submitted related servers found.

    Related Servers

    • TIMPS

      TIMPSs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.
      14 npm
      MIT

    • Claude Habitat

      Ydy4HYW7ExA
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that provides persistent project context, workflow management, and knowledge capture for AI coding agents. It enables agents to maintain structured memory across sessions by tracking project profiles, conventions, skills, and technical debt.
      7
      -

    • repomemory

      Lay4U
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
      47 npm
      MIT

    • myBrAIn

      lilium360
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.
      32
      MIT

    • toon-memory

      LuiggiVal08
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP memory server for AI coding agents to remember decisions, patterns, and bugs between sessions. Provides persistent memory with 37 MCP tools, multi-session coordination, and token-efficient recall.
      184 npm
      11
      MIT

    • lxDIG MCP

      lexCoder2
      F
      license
      B
      quality
      C
      maintenance
      MCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.
      39
      4
      -
    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

    B3.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have distinct, well-described purposes, but a few overlaps exist (e.g., trw_claude_md_sync as a deprecated alias for trw_instructions_sync, and trw_before_edit_hint vs trw_before_edit_hint_batch). One tool lacks a description entirely (trw_mcp_security_status), causing ambiguity. Overall, descriptions are detailed enough to distinguish the majority.

    Naming Consistency4/5

    All tool names consistently use the 'trw_' prefix and snake_case, which is predictable. However, the pattern varies between verb_noun (e.g., trw_adopt_run), noun (e.g., trw_status), and noun_noun (e.g., trw_code_symbol), with no strict adherence to a single convention. The consistency is good but not perfect.

    Tool Count2/5

    41 tools is excessive for most MCP servers, far exceeding the typical 3-15 well-scoped range. While the server attempts to cover a broad framework, many tools are highly specific or deprecated, suggesting the surface could be streamlined. Agents may struggle to navigate this many options efficiently.

    Completeness4/5

    The tool set covers a wide range of TRW framework needs: run lifecycle, learnings, code indexing/search, PRD management, validation, reviews, and probes. Minor gaps exist (e.g., no explicit run deletion or listing), but the core workflows are well-supported. The surface is comprehensive for its intended domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources