Skip to main content
Glama
padobrik

MCP Context Graph

by padobrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Context Graph

No user-submitted related servers found.

    Related Servers

    • Multi-Agent Memory MCP

      jhunter11
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides local-first persistent memory with a typed knowledge graph and bounded multi-hop retrieval via MCP, letting coding agents and local LLM systems store, search, and recall facts across sessions without hosted services or model dependencies.
      MIT

    • kg-memory-mcp

      arunmenon
      F
      license
      Not graded
      quality
      C
      maintenance
      An in-memory knowledge graph MCP server that gives coding agents structural and semantic recall over codebases by indexing Python source, ADR documents, and project configuration, exposing 7 tools for search, traversal, context retrieval, and natural-language Q&A.
      -

    • gbrain

      laozhong86
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first compiled knowledge graph MCP server that provides structured memory for AI agents with full-text search, vector embeddings, and timeline tracking.
      287 npm
      8
      MIT

    • Graph-Mem MCP

      Sathvik-1007
      A
      license
      Not graded
      quality
      A
      maintenance
      A universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.
      1
      MIT

    • Mnemograph

      tm42
      A
      license
      A
      quality
      D
      maintenance
      A persistent, event-sourced knowledge graph MCP server for AI coding agents that enables semantic search, tiered context retrieval, and git-based version control of AI memory.
      31
      2
      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

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: indexing, symbol lookup, caller analysis, context retrieval, source expansion, and graph dumping. There is no overlap that would cause an agent to select the wrong tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., find_symbol, get_context). The verbs are descriptive and uniform, making the toolset predictable.

    Tool Count5/5

    Six tools is a well-scoped size for a code graph server, covering core operations without excessive fragmentation or missing essential functionality. Each tool earns its place.

    Completeness5/5

    The toolset covers the full workflow: indexing, symbol discovery, relationship analysis, source retrieval, and graph visualization. There are no significant gaps for the stated purpose of providing code context.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources