Fresh, attributed facts from your sources β cached, and invalidated the moment a source changes.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Real-time, provenance-invalidated context for AI agents & RAG.
Build understanding once. Reuse it everywhere. Keep it fresh β automatically.
π Documentation Β Β·Β coalent.ai Β Β·Β π¬ Discord
Quickstart Β· What's new in v0.6 Β· Gate ladder Β· Bring your own stack Β· MCP Β· LangChain Β· Benchmark Β· CLI
Your agent re-reads the same sources on every call β and the moment a source changes, every cached answer is silently wrong.
Coalent builds the understanding once, caches it by what the query means, and invalidates it surgically the instant an underlying source changes. As correct as re-reading everything, at a fraction of the cost β and never stale.
Every context layer is forced to trade off three things. Coalent is built to hold all three at once:
Coalent sits above retrieval β bring any retriever (vector DB, hybrid search, GraphRAG, tools, APIs). It's the freshness-and-reuse layer, not another retriever β deliberately the opposite of GraphRAG's build-the-whole-graph-upfront tax: lightweight, independent units, built lazily only when a query actually needs one, and refreshed by dirtying a single unit (no graph surgery).
New in v0.6 β the pool read path (
read_path="pool"): every read serves the token-budgeted, globally ranked fresh-claim pool. Measured on a 605-question news benchmark (strict grading): 0.731 accuracy @ 981 context tokens β matching naive top-9 (0.711 @ 1,311) at ~25% fewer tokens, and naive's best measured point (top-12: 0.731 @ 1,729) at ~43% fewer. Plus a default-OFF behavioral stack β residual spans β refusal fallback β append-only repair β query keys β measured at β33% refusals and +3.1 pts on the same store. All opt-in; the default read path is unchanged v0.5 behavior. See What's new.New in v0.6.1 β the MCP server:
coalent-mcpputs the cache one line away from Claude Code, Cursor, or any MCP client (Use it from Claude Code / Cursor), andlangchain-coalentmakes your existing LangChain stack the cache's substrate. Both additive-only.
Runs as-is β StubSynthesizer needs no API key, so you can feel the loop in ten seconds:
Wire in a real model β any text-in / text-out LLM works. In v0.4 the synthesizer builds extractive understanding by default (query-independent atomic claims that keep every fact), and the cache does cross-unit recall β both on automatically:
The v0.6 pool read path β opt in, and every read serves the budget-packed, globally ranked fresh-claim pool instead of one routed unit. Attribution is the one thing to wire: a 3-line pool_header callable mapping each unit to [title | source | date] from your own corpus metadata. This is the measured golden path β on a 605-question news benchmark (strict grading), 0.68 accuracy with the bare built-in header vs 0.73 with this callable, same store, same queries:
Runnable no-API-key demo, including the refusal loop: examples/pool_read_path.py.
coalent-mcp serves fresh, attributed facts from a Coalent cache to any MCP client β
and the facts are invalidated the instant their source changes. One line to wire it into
Claude Code:
(Cursor / Claude Desktop / any MCP client: register the same coalent-mcp ... command in
its MCP config.)
Bring your own cache (--cache-factory module:function) β the primary mode. Your
factory returns a fully constructed SemanticCache: your vector DB, your embedder, your
LLM, every knob. The server adds protocol glue only β and the glue is measured to add
zero quality loss: factory mode reproduced the library's own benchmark result
byte-identically (0.710 on a 100-question validation run drawn from our n=605 news
benchmark β identical CIs, 100/100 serves, 98/100 answer payloads byte-equal to the
library run).
Freshness here is signal-driven: your ingestion pipeline calls the source_changed tool
when a document changes and the affected facts invalidate immediately. (Adding
--watch DIR alongside the factory also fires it on file edits β invalidation only; it
never ingests into your index, and it matches only when your artifact ids equal the
watch-relative paths.)
Zero-config folder mode (--watch DIR) β the demo wedge. Point it at a folder of
docs and you get the recommended v0.6 deployment (pool path, residual spans, query keys,
SQLite persistence, automatic [path | modified date] attribution) with no code at all:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/coalent)<a href="https://allmcps.com/mcp/coalent"><img src="https://allmcps.com/api/badge/coalent?style=directory" alt="Coalent on AllMCPs" /></a>