docbrain-ai/docbrain
DocBrain makes documentation improve itself.
Platform-specific configuration:
{
"mcpServers": {
"docbrain": {
"command": "npx",
"args": [
"-y",
"docbrain"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
<p align="center"> </p>
<p align="center"> <strong>Stop writing docs after the fact. Capture knowledge where it happens.</strong><br/> DocBrain intercepts knowledge at the moment of creation — from PRs, Slack threads, CI pipelines, and IDE sessions — then scores, reviews, and publishes it before anyone has to ask "where's the doc for this?" </p>
<p align="center"> <a href="https://docbrainapi.com"></a> <a href="https://github.com/docbrain-ai/docbrain/stargazers"></a> <a href="LICENSE"></a> <a href="https://glama.ai/mcp/servers/docbrain-ai/docbrain"></a> </p>
<p align="center"> <a href="https://docbrainapi.com"><strong>Website</strong></a> • <a href="https://docbrainapi.com/docs"><strong>Docs</strong></a> • <a href="#quickstart">Quickstart</a> • <a href="#the-problem">The Problem</a> • <a href="#how-docbrain-fixes-it">How It Works</a> • <a href="#features">Features</a> • <a href="#architecture">Architecture</a> • <a href="#security-architecture">Security</a> </p>
---
> Project Status: DocBrain is currently distributed as pre-built Docker images and deployment artifacts (Helm charts, configuration, documentation). Source code is not yet published. Contributions are welcome for documentation, configuration, and bug reports.
---
You know this cycle. Every engineering team does.
Monday: Senior engineer explains the retry logic in a PR review. Three people learn it. The knowledge lives in a GitHu
Loading reviews...