MCP Code Flow Analyzer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Root path of the project to analyze. Defaults to the current working directory if not set. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| traceBusinessFlowA | Trace the complete business flow chain from an entry point. Returns real call graph (parsed from function bodies), critical operations (DB/HTTP/file I/O), and a Mermaid diagram. Supports fuzzy matching and Chinese keywords like "登录"/"支付". |
| findCallersA | Find all functions that call a given function (reverse call graph) |
| getCriticalPointsA | Get all critical operations (database reads/writes, HTTP requests, file I/O, exec calls) reachable from a function. This is the unique value of MCP vs raw search — it semantically classifies what each function actually DOES. |
| generateFlowDiagramB | Generate a Mermaid call graph diagram for a function. Output renders in any markdown viewer (GitHub, VSCode, etc.). |
| searchSymbolsA | Fuzzy search for symbols. Supports partial names, Chinese keywords ("登录", "支付"), and CamelCase prefixes. |
| whoTriggersA | Reverse trace: find all entry points (controllers/public methods) that eventually call a given function. Answers questions like "what endpoints write to the order table?" by reverse-BFS from a critical operation. |
| getProjectInfoB | Get project statistics: file count, symbol count, critical point count, languages detected |
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 7 tools
Most tools have distinct purposes, but there is some overlap between findCallers and whoTriggers, and between generateFlowDiagram and traceBusinessFlow. Descriptions help differentiate, but agents might occasionally confuse them.
All tool names follow a consistent verb_noun pattern in camelCase (e.g., findCallers, generateFlowDiagram), making them predictable and easy to understand. 'whoTriggers' is slightly different but still verb-like.
With 7 tools, the server is well-scoped, covering essential code flow analysis functions without being overwhelming. Each tool serves a clear role.
The tool set covers search, call graph analysis, critical point detection, and visualization. Minor gaps exist, such as lacking a tool for comparing flows or detailed function metadata, but it sufficiently handles core analysis tasks.