Schema | MCP Code Flow Analyzer

MCP Code Flow Analyzer

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.

Features and capabilities supported by this server

Capability	Details
`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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bsdnn/mcp-code-flow-analyzer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server