cpp-coro-graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB | No | Path to the cpp-coro-graph database file (e.g. /path/to/repo/.cpp-coro-graph/graph.db). If not provided, the MCP server will search upward from the working directory for .cpp-coro-graph/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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ccg_statsA | cpp-coro-graph: node/edge counts by kind and device. Optional by_namespace=true for per-namespace symbol counts. Call first to confirm the graph DB is loaded. |
| ccg_queryB | Search symbols or file nodes by name/qname/path fragment. Use kind=file for files; namespace= for C++ namespace filter (exact or nested prefix). Empty query + namespace lists that module. |
| ccg_nodeC | One symbol or file: location + related edges. Symbols → callers/callees (control). Files → contains (symbols) + includes (headers) + importers. |
| ccg_callersB | Who calls / awaits this symbol (incoming control edges). |
| ccg_calleesB | What this symbol calls / awaits (outgoing). Ordered by source line (#1,#2). |
| ccg_seqA | Ordered calls/await sequence inside a function (by source line). Preferred over explore edge_kind=seq for understanding in-function order. |
| ccg_exploreC | Neighborhood around a symbol: in/out + optional BFS depth (like codegraph explore for coroutines). |
| ccg_pathC | Shortest path between two symbols (control) or two files (includes). Use file:path or *.hpp queries for include topology. |
| ccg_impactC | Incoming blast radius. Symbols: callers. Files (file:… / *.h): importers via #include. |
| coro_statsC | Alias of ccg_stats. |
| coro_exploreD | Alias of ccg_explore (legacy). |
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
Many tools have clear distinct purposes (stats, query, node, callers, callees, seq, path, impact), but ccg_explore and ccg_seq overlap with ccg_node's related edges and callers/callees, creating some ambiguity. The presence of aliases (coro_stats, coro_explore) adds confusion for an agent.
Most tools follow a consistent ccg_verb or ccg_noun pattern (ccg_stats, ccg_query, ccg_node, ccg_callers, etc.), which is predictable. However, the aliases coro_stats and coro_explore deviate from the ccg_ prefix, slightly breaking consistency.
11 tools is a reasonable count for a graph-based code analysis server covering stats, query, traversal, and impact. The two aliases are redundant but don't bloat the count excessively.
The tool set covers essential operations: graph stats, symbol/file lookup, edge exploration (callers, callees, sequence), path finding, and impact analysis. It lacks explicit filtering or aggregation tools, but the core analysis surface is well-covered for a read-only graph explorer.