Video wird geladen...
Video konnte nicht geladen werden
Introducing the Knowledge Base MCP. Greptile maintains a detailed knowledge base of how every part of your codebase works, as well as a history of past incidents. Starting today coding agents like Codex, Claude can access the Knowledge Base via Greptile's MCP, so they can use Greptile's learnings to... show more
64,850 Aufrufe • vor 9 Tagen •via X (Twitter)
22 Kommentare

Learn more:

Yalls dont stop shipping do you. Love it team

Greptile knowledge base is slept on. It's so powerful having all the context in one place & constantly evolving

Does it work on historical? Lots of reviews behind me.

Damnnn this is fire

Incident history inside the coding loop is a useful addition.

This is where agent memory starts becoming real infrastructure. The next challenge is making that accumulated knowledge structured, versioned, and traceable — so agents don’t just remember what happened, but understand how that knowledge evolved and where it came from.

production quality on this is crazy

awesome!

the history-of-incidents bit is what i actually want. most mcp demos can answer a file question, but the "why did we do this weird thing" context is the part i keep missing — does it update itself from prs or only docs?

the useful boundary is not 'agent can read the codebase.' it is whether each retrieved fact carries provenance, freshness, and an owner. otherwise a knowledge base becomes another prompt-shaped authority with no way to tell stale guidance from a current constraint.

does the incident history get pulled in automatically or does someone still have to write the postmortem

hooking an mcp incident log directly into the subagent prompt stops it from making the same breaking imports twice.

past incidents in the MCP. did not expect that

most codebase context tools tell the agent how things work. knowing how it broke last time is a step past that

How do you prevent stale architectural knowledge from becoming authoritative context for the agent?

What is the difference between it and things like onsidian git that is free and most common for users ?.

fire

How much will this cost?

Interesting. So all the code base replicates to greptile?

past incidents remembered, that's smart

This is the missing piece for coding agents. Giving them a living map of the codebase and past incidents is how they stop guessing and start helping for real.



