Skip to main content
Glama
yesheng-oss

Context-MCP

by yesheng-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Context-MCP

No user-submitted related servers found.

    Related Servers

    • context-mcp

      vibhasdutta
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent memory and a codebase knowledge graph for AI coding assistants, enabling shared context across multiple tools like Claude, Cursor, and ChatGPT, with significant token reduction.
      5
      13 npm
      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.
      18 npm
      2
      MIT

    • hive-memory

      moonx010
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with persistent, graph-connected memory across projects, enabling cross-project context retrieval via synaptic connections and hybrid search.
      12 npm
      6
      MIT

    • CodeMind

      twly7ho2
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent codebase memory and semantic context for AI agents via AST-aware chunking and symbol graph indexing.
      1
      -
    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.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a clearly different job—build, query, contextualize, report, list, visualize, impact, filter, architectural map—but some overlap exists: codegraph_query and codegraph_context both return graph context, and codegraph_nodes is essentially a restricted version of codegraph_filter. The descriptions are strong enough that an agent can usually choose correctly.

    Naming Consistency4/5

    All tools share the consistent codegraph_ prefix and snake_case, and the suffixes are short and readable. However, they mix verb-style suffixes (build, query, filter) with noun-style suffixes (context, report, nodes, html, arch), so the set is not a strict verb_noun pattern.

    Tool Count5/5

    Nine tools is well within the ideal range and appropriate for a code-graph server. Each tool corresponds to a distinct workflow: building, querying, contextualizing, reporting, listing, visualizing, impact analysis, filtering, and architectural mapping.

    Completeness5/5

    The tool surface covers the full lifecycle of a code knowledge graph: build, inspect, filter, query, analyze impact, generate reports, and export visualization. There are no obvious missing operations that would block an agent from using the graph effectively; rebuild-on-change is handled via codegraph_build.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources