MCP VFX Ecosystem — Knowledge Graphs

Interactive code-structure graphs (AST) for the three MCP servers · auto-rebuilt and published by GitHub Actions on every push that touches src/**

✓ All graphs healthy. 1214 nodes / 2613 edges across the three servers, grouped into 66 communities. Fully connected except 2 benign package __init__.py markers in flame-mcp (no functions/classes → no AST edges; not dead code).

server	nodes	edges	communities	isolated	graph
fpt-mcp	505	1302	30	0	open
maya-mcp	309	592	13	0	open
flame-mcp	400	719	23	2*	open
total	1214	2613	66	2*

* both isolated nodes are package __init__.py markers — expected, not dead code.

fpt-mcp

ShotGrid / Flow Production Tracking client · 505 nodes · 30 communities

◉ Interactive graph ▤ Report (md)

maya-mcp

Autodesk Maya automation via Command Port · 309 nodes · 13 communities

◉ Interactive graph ▤ Report (md)

flame-mcp

Autodesk Flame compositing via bridge · 400 nodes · 23 communities

◉ Interactive graph ▤ Report (md)

Community names: the live graphs name communities with Gemini only when each repo has a GEMINI_API_KEY Actions secret. Until it is set they show generic Community N (the graph structure, sizes and layout are unaffected). Add the secret to fpt-mcp / maya-mcp / flame-mcp and the next push (or a manual re-run) names them.

Built with graphify (AST extraction, code-only) · force-directed layout tuned for fewer edge crossings · each graph also redeploys automatically when its server's src/** changes.