CSG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CSG_DB | Yes | Absolute path to the prebuilt SQLite graph database used by csg-mcp, e.g. /abs/graph.db |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tusA | 列出真实参与编译的翻译单元（TU）及其完整编译参数。回答"哪些文件真正被编译了"。 |
| list_entitiesA | 列出指定源文件中定义的全部实体（函数/变量/类型），按行号排序。 |
| search_entitiesB | 按名称模糊搜索符号（FTS5 全文检索），如 search_entities('parse_*')。 |
| get_definitionC | 获取符号的定义位置（文件:行号）及实体信息。 |
| who_callsA | 查询哪些函数调用了 fn（编译器验证的反向调用边）。 |
| what_callsC | 查询 fn 调用了哪些函数（正向调用边）。 |
| blast_radiusC | 影响面分析：fn 变更会传播影响到哪些函数（按传播深度分层）。 |
| call_pathC | 搜索 a 到 b 的最短调用路径。返回调用链数组，无路径返回 null。 |
| file_issuesB | 查询指定文件的 Coverity 静态分析缺陷（CID/checker/严重级/位置/描述）。 |
| get_astB | 获取函数级 AST（CodeXM 模型 JSON）。需要索引阶段已导出该函数 AST。 |
| statusB | 索引状态：TU/实体/调用边/缺陷数量及构建时间。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.