Skip to main content
Glama
autumn-hh

Project Context MCP

by autumn-hh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Project Context 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

    • ctxmem

      DoppiaG93
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.
      3
      MIT

    • promem-mcp

      DIP-RO
      A
      license
      B
      quality
      A
      maintenance
      Enables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.
      13
      MIT

    • mcp-light-memory

      PeterPirog
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.
      MIT

    • codemem

      jeang42
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.
      2
      Apache 2.0
    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.3/5.0

    Scored across 34 tools

    Disambiguation5/5

    Tools are grouped by domain (project, memory, task, etc.) with distinct actions. Even within groups, each tool has a clear, non-overlapping purpose, e.g., memory_candidate_accept vs. memory_remember serve different lifecycles.

    Naming Consistency5/5

    All tools use a consistent verb_noun pattern with underscore_case, such as project_list, project_open, memory_remember, and task_checkpoint. The naming convention is uniform across all 34 tools.

    Tool Count2/5

    34 tools is well above the typical 3-15 range for a well-scoped server. While the domain coverage is broad, the sheer number may hinder agent navigation and selection.

    Completeness4/5

    The tool set covers most lifecycle operations for projects, memories, tasks, and user memories, including backups, indexing, health checks, and search. Minor gaps like in-memory candidate updates exist, but overall it's thorough.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources