Skip to main content
Glama
kawacode-ai

Kawa Code MCP

Official
by kawacode-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Kawa Code MCP

No user-submitted related servers found.

    Related Servers

    • Waystone

      hb407033
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding assistants to contribute to and query a team-shared project memory, storing human-confirmed decisions with source and scope so work can continue across machines.
      12
      Apache 2.0

    • memfed

      fpolica91
      A
      license
      Not graded
      quality
      A
      maintenance
      Federated, privacy-first shared memory for AI coding assistants that lets you capture, review, and share team knowledge via git without a central server.
      4 npm
      Apache 2.0

    • team-memory-mcp

      gustavolira
      A
      license
      Not graded
      quality
      D
      maintenance
      Shared team memory for AI coding agents with Bayesian confidence scoring and temporal decay, enabling persistent storage and retrieval of engineering patterns across sessions.
      11 npm
      13
      MIT

    • Projectmem

      riponcm
      A
      license
      A
      quality
      A
      maintenance
      Local-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.
      17
      330 PyPI
      833
      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.9/5.0

    Scored across 25 tools

    Disambiguation4/5

    Tools are mostly distinct, with clear descriptions differentiating similar ones like get_session_decisions and get_project_decisions. However, there is some potential confusion between check_active_intent and get_intent_changes, and between pre_edit_decision_check and pre_edit_acknowledge, though descriptions help.

    Naming Consistency4/5

    All tool names use snake_case, which is consistent. However, the naming pattern varies: some use verb_noun (e.g., check_active_intent), while others use more complex prefixes like pre_edit_ or arbiter_. This minor inconsistency prevents a perfect score.

    Tool Count3/5

    25 tools is on the higher end, but the scope of the server—managing intents, decisions, and conflicts—justifies the count. Some tools could be merged (e.g., get_session_decisions and get_project_decisions), but overall the number is reasonable for the domain.

    Completeness4/5

    The tool surface covers the full lifecycle of intents and decisions, including creation, activation, tracking, conflict detection, and resolution. Minor gaps exist, such as no tool to list all active intents (only team intents), and no direct deletion tool for intents, but these are manageable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources