TigerGraph GraphRAG v2.0: Agentic Chat, MCP Tools, and Structure-Aware Chunking
GraphToolsTigerGraph GraphRAG v2.0
On 1 July 2026, TigerGraph released GraphRAG v2.0, a major update to their open-source GraphRAG framework. The release introduces three capabilities that shift GraphRAG from a retrieval pattern to a autonomous reasoning layer: an agentic chat engine, external MCP tool integration, and structure-aware document chunking.
Agentic Chat Engine
The headline feature is the agentic chat engine, which operates in two modes:
Planner mode decomposes a user query into a retrieval plan before executing any search. Given a complex question — "What is our aggregate supply chain exposure to the new EU battery regulations across all Asian suppliers?" — the planner identifies the entities involved (suppliers, regulations, components, products), the relationships to traverse (supplies, regulated-by, contains), and the order of operations. It then executes each retrieval step and assembles the results into a coherent context window for the LLM.
Reactive mode starts with an initial retrieval, evaluates whether the returned context is sufficient to answer the question, and iteratively expands the search along graph edges until it has enough evidence. This is analogous to how a human researcher reads an initial result, identifies gaps, and follows references.
| Feature | Planner Mode | Reactive Mode |
|---|---|---|
| Query approach | Decompose-then-retrieve | Retrieve-then-evaluate-then-expand |
| Best for | Known-complex queries with clear structure | Exploratory queries where the path is uncertain |
| Latency | Higher initial latency, fewer iterations | Lower initial latency, may need more iterations |
| Determinism | Fully deterministic plan | Path-dependent |
MCP Tool Integration
GraphRAG v2.0 integrates with the Model Context Protocol, allowing the chat engine to invoke external tools during the retrieval process. The agentic engine can call out to:
- External knowledge bases and document stores via vector search
- Enterprise APIs (CRM, ERP, ticketing systems) to enrich graph context
- Code execution environments for dynamic analysis
- Web search for current-events grounding
Each MCP tool is registered with a schema describing its inputs, outputs, and cost profile. The planner selects tools based on the retrieval plan; the reactive engine discovers tools as needed based on context gaps.
Structure-Aware Document Chunking
Previous GraphRAG implementations used fixed-size or semantic-similarity chunking, which frequently splits document sections across chunk boundaries, losing the structural context that graphs need. V2.0 introduces structure-aware chunking that respects document hierarchy:
# Example configuration for structure-aware chunking
{
"chunking": {
"strategy": "structure_aware",
"boundaries": ["h1", "h2", "h3", "table", "list"],
"min_chunk_size": 256,
"max_chunk_size": 2048,
"preserve_tables": true,
"preserve_code_blocks": true
}
}
Chunks align with document sections, tables, and code blocks, ensuring that entities extracted from a chunk have the correct section-level context. This improves entity disambiguation and relationship extraction quality, particularly for technical documentation where meaning depends on section context.
Deployment Architecture
V2.0 introduces an additive prompt customisation system that allows enterprise teams to inject domain-specific instructions into each stage of the retrieval pipeline without forking the codebase. Prompts can be configured per graph, per user role, or per retrieval mode.
The release also includes a knowledge graph compatibility check and repair tool that automatically detects and fixes schema drift when graph structure changes between indexing runs — a practical improvement for production deployments where graph schemas evolve.
Enterprise Value
For teams already running GraphRAG in production, v2.0's agentic engine changes the operational model from "ask the right question" to "describe the goal." The planner and reactive modes handle retrieval strategy selection, reducing the need for query engineering. The MCP integration extends reach beyond the knowledge graph without leaving the GraphRAG execution context.
The release is available at github.com/tigergraph/graphrag under a permissive license, with documentation covering migration from v1.x and configuration guides for the new agentic modes.