One current understanding for every agent.
Each CodeSummary site can expose a Model Context Protocol endpoint grounded in the documentation your team reviews and the codebase map maintained behind it.
The working loop
Set it up once. Keep the knowledge moving.
- 01
Open the MCP tab
Every documentation site has its own endpoint. Private sites also provide scoped access controls from the same screen.
- 02
Connect an agent
Add the endpoint to any compatible agent or development environment using the standard HTTP transport.
- 03
Ask with context
The agent can answer product questions, find relevant code, and cite the source material behind its response.
One knowledge source
Product answers and code context belong together.
Documentation explains intended behavior. The codebase map shows where that behavior is implemented. CodeSummary makes both available through one maintained endpoint so an agent does not have to choose between polished prose and source-level evidence.
The endpoint can answer a product question with citations, orient an agent toward the files relevant to a task, locate symbol definitions and references, and retrieve the underlying documentation when deeper reading is useful.
Scoped access
One endpoint per site, with privacy that follows the docs.
Public knowledge can be available without credentials. Team-only knowledge requires an access token that can be issued and revoked independently from the dashboard.
Access stays attached to the documentation site, which keeps product boundaries clear when a workspace contains several teams, customers, or services.
Purpose-built tools
The agent asks for an answer, not a folder of files.
A generic retrieval endpoint pushes the reading and synthesis work back onto the agent. CodeSummary exposes focused tools that return the shape of context the task actually needs.
That means less exploratory work before implementation begins, shorter context windows, and responses that can be checked against the current source instead of accepted on faith.
askAnswer a product question with supporting documentation.
orientRank the code and context relevant to a planned change.
lookupLocate a symbol definition and the places that depend on it.
searchFind the exact page or concept when direct retrieval is better.
Put it to work
Turn the next code change into useful knowledge.
Start with one repository. Review the result before anything is published.