Augment Code has made its Context Engine available as a standalone MCP server that any agent can use. It builds a semantic index of the codebase and answers the agent's questions about the code. There's a local mode and a remote mode, where default branches are indexed through a GitHub App. In Augment's own test on 300 Elasticsearch pull requests, quality improved by more than 70%.
AI Council solves a neighboring problem. Besides the code, it stores what the code doesn't say: decisions, reasons, team rules. And it doesn't wait for the agent to ask. Rules and knowledge arrive through hooks when the agent opens or changes a file.
| Augment Context Engine | AI Council | |
|---|---|---|
| What the agent gets | Semantic search and code context | Code graph, decisions with reasons, rules, ticket breakdowns |
| Who starts it | The agent calls an MCP tool | Hooks deliver on their own; MCP on request; the KB gate keeps the agent from editing blind |
| Team rules | Not the focus | MUST and SHOULD tied to code, plus checks in branch review |
| Branches | Remote mode indexes default branches | Knowledge on any git branch, moves to the target after merge |
| Freshness | Code re-indexing | Code re-indexing plus re-checks of knowledge entries, with labels |
| Deployment | Augment cloud or local mode | Cloud or self-hosted; air-gapped on Enterprise |
Augment Context Engine details are based on the vendor's public documentation and website as of October 2026: Context Engine MCP announcement. If anything has changed, let us know and we will correct it.
Connect a real repository and see how the platform behaves on your code, not on a canned demo.