callgraph-mcp 1.4.8 → 1.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -24,10 +24,10 @@ Most AI coding tools answer structural questions about your codebase by reading
|
|
|
24
24
|
|
|
25
25
|
**callgraph-mcp eliminates all three.** It never reads your code as prose. It parses every file into an AST using Tree-sitter, builds an exact directed call graph, and answers structural queries against that graph. Every caller, every callee, every reachable function, every cycle - returned as a precise index. The answer is always the same regardless of how large your codebase is, which files happen to be in context, or how deeply buried a function is. **There is no probability involved. There is no attention to dilute.**
|
|
26
26
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
27
|
+
|
|
28
|
+
*The image shows how callgraph explains the POST method flow in python-fastAPI codebase irrespective of how large or small the codebase is.*
|
|
30
29
|
|
|
30
|
+
---
|
|
31
31
|
|
|
32
32
|
## Setup
|
|
33
33
|
|
|
@@ -121,8 +121,6 @@ Optional parameters shown in `[brackets]`.
|
|
|
121
121
|
|
|
122
122
|
## Example Use Cases
|
|
123
123
|
|
|
124
|
-
---
|
|
125
|
-
|
|
126
124
|
### PR review and change safety
|
|
127
125
|
|
|
128
126
|
> *"I just modified `processPayment`. Without reading any code, tell me every function that could break and rank them by how many hops away they are from the change."*
|