Skip to main content
Glama
yuejunwei1989

CSG MCP Server

by yuejunwei1989
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CSG MCP Server

No user-submitted related servers found.

    Related Servers

    • Kivgraph

      Luqueee
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to query a semantic cross-repository code graph for symbols, references, callers, dependencies, and change impact across registered repositories.
      12
      23
      Apache 2.0

    • engram-serve

      markw65142
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a local structural code graph for focused context, including relevant source entities, Git relationships, call paths, impact, and recorded mistakes. It exposes this context so agents can investigate code and retrieve bounded context before reading full files.
      9 npm
      MIT

    • MindGraph

      dycm8009
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.
      15 npm
      MIT

    • engram-serve

      olgaito59557
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and IDEs to query a local structural code graph and retrieve focused, token-bounded context on code entities, Git relationships, callers/callees, impact, paths, and recorded mistakes for more efficient sessions.
      9 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a clearly distinct query type: entity listing/searching, definitions, call-graph directions, impact analysis, call paths, static-analysis defects, ASTs, index status, and translation units. who_calls vs. what_calls and blast_radius vs. call_path are explicitly differentiated by direction and analysis purpose.

    Naming Consistency4/5

    All names use snake_case consistently, and most follow a readable verb_noun or query pattern. Minor deviations exist in noun-only names like blast_radius, call_path, file_issues, and status, but they remain clear and predictable within the set.

    Tool Count5/5

    Eleven tools are well-scoped for a code-intelligence and static-analysis server, covering entities, call graphs, defects, ASTs, and build artifacts without obvious redundancy. Each tool appears to earn its place.

    Completeness4/5

    The surface covers core code-analysis workflows: symbol lookup, definitions, callers/callees, impact paths, Coverity defects, ASTs, status, and translation units. Minor gaps exist, such as global defect search/listing or general file/source retrieval, but agents can largely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources