← Back to research
·12 min read·company

Augment Context Engine

Augment Code unbundled its flagship semantic-indexing context engine as an MCP server any coding agent can call — GA February 6, 2026, with local (Auggie CLI) and hosted cross-repo modes. Vendor benchmarks claim 70%+ agent improvement (Claude Code + Opus 4.5: 80%), backed by $252M in funding.

https://www.augmentcode.com/product/context-engine-mcp ↗
coding-agentscode-intelligencecontext-engineeringdeveloper-toolsmcpgithub

Key takeaways

  • Augment Code took the semantic-indexing engine behind its AI coding assistant and shipped it as a standalone MCP server on February 6, 2026 — any MCP-compatible agent (Claude Code, Cursor, Codex, Zed, Kilo, Roo, and more) can now call it for codebase retrieval
  • Vendor-run benchmarks on 300 Elasticsearch PRs (900 attempts) claim 70%+ quality improvement across agents, peaking at 80% for Claude Code + Opus 4.5 — striking numbers, but self-reported and on a single repository
  • Two modes: local (the Auggie CLI as a stdio MCP server with real-time working-directory indexing) and remote (Augment-hosted engine over HTTP with GitHub App integration for cross-repo and CI context)
  • The company behind it raised a $227M Series B at a $977M valuation in April 2024 ($252M total) from Sutter Hill, Index, Lightspeed, Innovation Endeavors, and Meritech — unusually deep pockets for a context tool

FAQ

What is the Augment Context Engine MCP?

It is Augment Code's proprietary semantic code-search and indexing engine, unbundled from its coding assistant and exposed as an MCP server so any MCP-compatible coding agent can query it for codebase context.

How much does the Augment Context Engine cost?

MCP usage is token-based — LLM tokens at provider rates plus a 40% service fee, averaging roughly $0.03–$0.06 per query — with 1,000 free queries at launch; Augment's broader credit plans run $20–$200/month.

How does local mode differ from remote mode?

Local mode runs the Auggie CLI on your machine as a stdio MCP server that indexes your working directory in real time; remote mode connects to an Augment-hosted engine over HTTP that auto-indexes selected repos' default branches via a GitHub App, enabling cross-repo and CI context.

How is it different from Serena or Repomix?

Serena and Repomix are free, open-source, and fully local (LSP symbols and context packing respectively), while Augment's engine is a paid, closed-source semantic index with a hosted cross-repo mode and vendor-published benchmark claims behind it.

Executive Summary

Augment Context Engine MCP is the unbundling of Augment Code's core asset: the proprietary semantic-indexing engine that powered its AI coding assistant is now a standalone MCP server that any agent — Claude Code, Cursor, Codex, GitHub Copilot, Zed, Kilo Code, Roo Code, Gemini CLI, and others — can call for codebase retrieval.[1][2] It went GA on February 6, 2026, with two modes: a local mode where the Auggie CLI runs as a stdio MCP server indexing your working directory in real time, and a hosted remote mode at api.augmentcode.com/mcp that auto-indexes selected repositories' default branches via a GitHub App for cross-repo and CI context.[1][2]

The launch pitch is a benchmark: on 300 Elasticsearch PRs across 900 attempts, Augment reports that adding the Context Engine improved agent output quality by 70%+ across agents — 80% for Claude Code + Opus 4.5, 71% for Cursor + Opus 4.5, 30% for Cursor + Composer-1 — measured across correctness, completeness, best practices, code reuse, and unsolicited documentation.[1] These numbers are vendor-run, on a single repository, and should be read as such. The strategic shift is notable regardless: a $977M-valuation assistant vendor conceding the agent layer and selling context as the durable primitive — "a weaker model with great context (Sonnet + MCP) can outperform a stronger model with poor context (Opus without MCP)," in the company's own framing.[3][1]

AttributeValue
CompanyAugment Inc. (Augment Code), Palo Alto[3]
FoundersIgor Ostrovsky (ex-Pure Storage), Guy Gur-Ari (ex-Google AI researcher)[3]
Funding$252M total — $227M Series B at $977M post-money (April 2024) from Sutter Hill, Index, Innovation Endeavors, Lightspeed, Meritech; $25M Series A led by Sutter Hill[3]
Context Engine MCP GAFebruary 6, 2026[1]
Open SourceNo — proprietary engine; community wrappers exist[2][4]

Product Overview

The product is a single MCP tool, codebase-retrieval, backed by Augment's semantic index: the agent asks a natural-language question about the codebase and gets back the relevant code context, instead of burning turns on grep-and-read exploration.[2] Augment claims agents complete tasks up to 2x faster and consume fewer tokens overall because retrieval replaces exploratory file reading — vendor-reported, like the quality numbers.[5]

Beyond code repositories, Context Connectors extend the index to GitLab, Bitbucket, documentation sites, and custom sources; the product demo shows 4,907 files indexed across 5 sources.[5] Setup is self-serve from app.augmentcode.com/mcp/configuration, with 1,000 free queries offered during launch.[5]

Key Capabilities

CapabilityDescription
Semantic codebase retrievalNatural-language queries over a semantic index via the codebase-retrieval MCP tool[2]
Local real-time indexingAuggie CLI indexes the working directory with immediate file-change detection; no manual sync[2]
Hosted cross-repo contextRemote mode auto-indexes selected repos' default branches on push, for multi-repo questions and CI[2]
Context ConnectorsGitHub, GitLab, Bitbucket, documentation sites, custom sources[5]
Broad agent support12 documented client integrations including Claude Code, Cursor, Codex CLI, Zed, Copilot, Kiro, Kilo, Roo, Antigravity, Gemini CLI, OpenCode, Factory Droid[2]

Product Surfaces

SurfaceDescriptionAvailability
Local MCP serverAuggie CLI over stdio, real-time working-directory indexGA[2]
Remote MCP serverAugment-hosted engine over HTTP with GitHub AppGA[2]
Context Engine SDKProgrammatic access for building on the engineAvailable (docs published December 2025)[6]

Technical Architecture

Local mode keeps indexing on your machine — "our indexer runs locally on your machine," per the product page — and is the recommended mode for active development, since edits are reflected immediately.[5][2] Remote mode trades that locality for breadth: an Augment-hosted index that updates when commits land on default branches, suited to understanding unfamiliar code, cross-repository questions, and CI environments where no working directory exists.[2] The underlying ranking and embedding stack is not publicly documented, and the engine itself is closed source — before the official launch, a community member published their own MCP wrapper around the Auggie CLI to get at the engine, an early demand signal the GA product effectively absorbed.[4]

Key Technical Details

AspectDetail
DeploymentLocal (Auggie CLI, stdio) or Augment-hosted remote (HTTP); no self-hosted server option[2]
MCP toolscodebase-retrieval[2]
Integrations12 documented agent clients; GitHub App for remote indexing; GitLab/Bitbucket/docs connectors[2][5]
Open SourceNo — proprietary engine and index[2]

Strengths

  • The engine has an independent reputation — years before the unbundling, HN commenters consistently identified the context engine as Augment's differentiator, which makes selling it standalone credible rather than a pivot of desperation.[6]
  • Works with the agents developers already use — rather than competing with Claude Code and Cursor for the agent seat, it upgrades them; 12 documented integrations at launch.[2]
  • Cross-repo hosted mode is genuinely differentiated — local-only rivals (Serena, Repomix, CodeGraph-style indexers) cannot answer questions spanning dozens of repositories or serve CI; the GitHub App mode can.[2]
  • Published, reproducible-in-principle benchmark methodology — 300 real Elasticsearch PRs, 3 prompts each, 5 scored dimensions is more rigor than most context-tool marketing, even if self-run.[1]
  • Deep-pocketed vendor — $252M raised at a $977M valuation gives the engine more runway than the typical open-source context tool's single maintainer.[3]

Cautions

  • All headline numbers are vendor-reported — the 70%+/80% improvements come from Augment's own evaluation on one repository (Elasticsearch); no independent replication exists as of June 2026.[1]
  • Marketing figures have drifted — the product page now attributes the +80% Claude Code result to Opus 4.6 while the launch post said Opus 4.5, a small inconsistency that does not build confidence in precision.[5][1]
  • A 40% service fee on top of LLM tokens — every query bills the underlying tokens at provider rates plus 40%, roughly $0.03–$0.06 per query; agents that retrieve aggressively will compound this.[2]
  • Pricing trust deficit at the parent company — third-party analysis of r/AugmentCodeAI sentiment reports the 2025 credit-pricing migration "eroded trust," with departing users recommending flat-rate Claude Code Max instead.[7]
  • Closed source with no self-hosted server — remote mode puts your cross-repo index on Augment's cloud, and there is no auditable core; free local alternatives like Serena and Repomix exist for the privacy-sensitive.[2]
  • Strategic ambiguity — Augment still sells its own assistant; whether the MCP product gets first-class long-term investment or remains a funnel to the suite is unproven four months post-GA.[1]

What Developers Say

There is no dedicated HN launch thread for the Context Engine MCP as of June 2026 — the only direct story (the Context Engine SDK, December 2025) drew 2 points and zero comments. The engine itself, inside Augment's assistant, has a longer comment trail.[6]

"Augment's main value add is their context engine, and imo they do it really well." — kenforthewin on Hacker News, December 2025[6]

"The context engine is the magic sauce. It's miles ahead of all the other tools…" — evelant on Hacker News, May 2025[6]

"We used to use Augment Code at work which has a thing called Context Engine…" — parasti on Hacker News, May 2026, describing a team that has since moved to Claude Code[6]

On the critical side, one HN commenter in July 2025 dismissed the branding as "a fancy way of saying" they index code for navigation, while praising results on medium codebases but flagging reliability issues and cost; and CostBench's aggregation of r/AugmentCodeAI characterizes the consensus on the parent company's 2025 pricing migration as a rollout "handled poorly."[6][7]

Pricing & Licensing

TierPriceIncludes
Launch promoFree1,000 free queries during launch[5]
MCP usageToken-basedLLM tokens at provider rates + 40% service fee; ~$0.03–$0.06 per average query[2]
Indie$20/month40,000 credits/month (Augment plan)[7]
Standard$60/month130,000 credits/month, up to 20 users[7]
Max$200/month450,000 credits/month[7]
EnterpriseCustomCustom credit limits, unlimited users[7]

Licensing model: Proprietary, closed source; access via Augment account and MCP configuration at app.augmentcode.com.[2]

Hidden costs: The 40% service fee rides on top of model tokens you are already paying for; credit top-ups run $15 per 24,000 credits, expire after 12 months, and monthly credits do not roll over.[2][7]

Competitive Positioning

Direct Competitors

CompetitorDifferentiation
SerenaFree, open-source, fully local LSP-based semantic toolkit; symbol-level precision but no hosted cross-repo index or published agent-improvement benchmarks
CodeGraphKnowledge-graph approach — explicit structural relationships rather than semantic retrieval; open source and self-hostable where Augment is closed and managed
RepomixContext packing, not retrieval — flattens a repo into one AI-friendly file; zero cost and zero server, but no query-time semantic search
Sourcegraph / native agent searchClaude Code and Cursor ship their own grep/embedding search; Augment's bet is that its dedicated index beats built-ins by the margins in its benchmark[1]

When to Choose Augment Context Engine Over Alternatives

  • Choose Augment Context Engine when: you work across large or multiple repositories, want one retrieval layer shared by every agent your team runs, and accept paying per query for vendor-claimed quality gains.[2]
  • Choose Serena when: you want free, local, auditable symbol-level context with no per-query cost or cloud dependency.
  • Choose CodeGraph when: explicit dependency and call-graph structure matters more than semantic similarity.
  • Choose Repomix when: the codebase fits in the context window and packing once beats querying repeatedly.

Ideal Customer Profile

Best fit:

  • Teams running coding agents against large, old, or multi-repo codebases where built-in search demonstrably fails
  • Organizations already paying for Augment Code that can extend the same index to every MCP-capable agent
  • CI and automation pipelines that need codebase context without a local checkout, via the hosted mode[2]

Poor fit:

  • Privacy-sensitive teams unwilling to put a cross-repo semantic index on a vendor's cloud
  • Small single-repo projects where Repomix or an agent's native search is free and sufficient
  • Cost-sensitive workflows where a 40% token surcharge per retrieval compounds badly[2]

Viability Assessment

FactorAssessment
Financial HealthStrong on paper — $252M raised at a $977M valuation, though the Series B dates to April 2024[3]
Market PositionFirst-mover among well-funded vendors unbundling context as an MCP product; the engine's reputation predates the launch[1][6]
Innovation PaceHigh — SDK (December 2025), MCP GA (February 2026), Context Connectors, 12 client integrations within months[6][2]
Community/EcosystemThin for the MCP product specifically — no HN launch thread, sentiment mostly inherited from the assistant era, including pricing-migration resentment[6][7]
Long-term OutlookHinges on independent benchmark validation and whether agent vendors' native retrieval closes the gap[1]

The unbundling reads as a clear-eyed strategic call: the agent layer commoditized around Claude Code and Cursor, and Augment moved its real asset to where the buyers are. The open questions are empirical — nobody outside Augment has reproduced the 70%+ numbers — and structural: every agent vendor is improving native codebase search, so the paid retrieval layer must keep outrunning free built-ins to justify a 40% token surcharge.[1][2]

Bottom Line

Augment Context Engine MCP is the most credible paid entry in the code-intelligence category: a reputation-backed semantic engine, a hosted cross-repo mode nothing open-source matches, and benchmark methodology that is at least published — but every impressive number on the page is the vendor grading its own homework, and the parent company carries community baggage from its 2025 pricing migration. Pilot it on a codebase where your agent demonstrably flails; let the free alternatives win everywhere else.

Recommended for: Teams with large or multi-repo codebases who can A/B the quality gain themselves, and existing Augment customers extending the index to other agents.

Not recommended for: Single-repo projects, privacy-sensitive organizations, or anyone unwilling to pay a per-query surcharge before independent benchmarks exist.

Outlook: Watch for third-party replication of the Elasticsearch benchmark, whether the SDK spawns an ecosystem, and whether Claude Code's and Cursor's native retrieval erases the margin the business depends on.

Research by Ry Walker Research • methodology

Sources

Share on XShare on LinkedIn