Skip to content
VibekollenBETAVibekollen
VideoAI Engineer

Why Your Company Needs a Context Graph (and How to Build It) — Gil Feig, Merge

Your agent can tell you why one customer was upset. Ask which customers were upset last year, and it falls apart.

Gil Feig, co-founder and CTO of Merge, explains why every company needs a context graph, a company brain that brings together third-party data, structured context, memories and skills. Using the question "which customers were upset last week?", he shows why connecting a few MCP servers isn't enough: live API lookups can't search across large datasets, so you need a synced copy for semantic queries, alongside live calls for simple lookups. He walks through the architecture: a router, synced and live context, a summarizer, and skills and memory that encode how your company actually defines things like a happy customer. He covers four tiers of context including derived summaries, a decision flowchart for when to use cache or live data, and why every answer must keep track of where its data came from.

Open on YouTube →

The text is the source's own description of its publication. The content belongs to AI Engineer.

More from AI Engineer