# MCP server for repo behavior indexing — entrypoints, impact, context packs before the agent edits (FlowIndex)

> Source: <https://dev.to/aditi_chatterji_acb54593a/mcp-server-for-repo-behavior-indexing-entrypoints-impact-context-packs-before-the-agent-edits-bk7>
> Published: 2026-06-25 00:53:55+00:00

```
I've been using Cursor on non-trivial repos and kept hitting the same issue: the agent finds a file but misses routes, shared modules, and tests that should run after a change.
I built FlowIndex — a local CLI + MCP server that scans a repo and builds a behavior graph in SQLite (entrypoints, imports/calls, tests, git co-change). No embeddings, no SaaS, no LLM calls in the index itself.
Setup:
pip install "flowindex[mcp]"
In your project: flowindex init flowindex scan
Add to ~/.cursor/mcp.json (use your repo's absolute path for cwd):
{
"mcpServers": {
"flowindex": {
"command": "flowindex",
"args": ["mcp"],
"cwd": "/absolute/path/to/your/repo"
}
}
}
4. Restart Cursor — you get tools like get_change_impact, suggest_tests, make_context_pack, explain_entrypoint, get_repo_overview.
Example workflow: before editing payments/ledger code, ask the agent to use make_context_pack or get_change_impact on that file — it pulls from the local graph, not a generic file search.
Honest limits: static analysis + git heuristics only. Call paths resolve via imports but aren't compiler-grade. TS/JS is heuristic. Documented in the README.

MIT · pip install flowindex · https://github.com/adu3110/flowIndex

Curious if others use MCP for repo context and what tools you wish existed. Happy to fix setup issues if anyone tries it.
```