Use case
Build a Knowledge Base Agent
Answer natural language questions over internal documents, Notion pages, and code using retrieval-backed responses with source citations.
Every organization has documentation that nobody reads because nobody can find the specific answer they need in a wall of text. A knowledge base agent inverts this: you ask a question in plain English, the agent retrieves the relevant passages from your docs, and returns a direct answer with a citation. Engineering teams use these for internal runbooks. HR teams use them for policy questions. Customer success teams use them for product detail questions that do not belong in a public help center.
The stack
Each pick is a real entry on the index. Click any one for the full detail page.
- 1O OSS Document Index
Anything LLM
by Community
Why this: AnythingLLM handles ingestion, chunking, embedding, and retrieval across multiple document types: PDFs, markdown files, Notion exports, and plain text. It runs locally or on a small VPS, keeping sensitive internal docs off third-party infrastructure.
Full entry - 2M MCP Source Sync
Notion MCP Server
by Notion
Why this: Notion MCP keeps the knowledge base current by reading updated pages on a schedule and pushing changed content back into the AnythingLLM index. Without this sync, the agent answers based on stale docs within weeks.
Full entry - 3M MCP Code Documentation
GitHub MCP Server
by GitHub
Why this: For engineering knowledge bases, GitHub MCP pulls README files, inline comments, and architecture docs from repositories so the agent can answer questions about how the codebase works, not just what is written in Notion.
Full entry - 4A Agents Query Handler
Claude Code
by Anthropic
Why this: Claude Code orchestrates the retrieval-answer pipeline: parse the question, retrieve from AnythingLLM, format the answer with source citations, and handle follow-up questions within a session. It applies guardrails to stay within the indexed knowledge and flag questions it cannot answer.
Full entry - 5S Skills Web Source Augmentation
Webpage Info Skill
by Anthropic
Why this: For questions that touch public documentation or vendor APIs not in the internal index, the webpage-info skill fetches the relevant public page and includes it as a source in the response. This covers the gap between internal docs and external references.
Full entry
Get this running with Enterprise DNA.
Enterprise DNA stores the knowledge base configuration, index credentials, and document sync schedules as project-level settings in OPM so the setup is reproducible across team members and devices. The EDNA secrets store holds the AnythingLLM API key and any GitHub tokens for private repository access. New document sources get added through the EDNA project interface rather than by editing config files directly.
Get the Stack Blueprint
A printable architecture card with every tool, role, and rationale on one page.
Enter your email. We send one useful update per week. Unsubscribe any time.
In the print dialog, choose "Save as PDF" as the destination.
Alternative stacks
Different angles on the same outcome.
Customer Onboarding Agent
If the primary audience for the knowledge base is new customers rather than internal staff, the onboarding agent adds step-by-step progress tracking on top of the Q&A layer.
See the alternative AlternativeResearch Agent
For ad-hoc research that goes beyond internal docs and pulls from external sources, journals, and live web data.
See the alternativeOther use cases
More curated stacks from the index.
Build a customer support agent
A working customer-support agent that triages tickets, answers from your docs, and escalates with full context.
See the stack Use caseBuild a research agent
An agent that watches sources, synthesises findings, and ships you a briefing on the days something matters.
See the stack Use caseBuild a sales outreach agent
An outreach agent that drafts personal-feeling email, qualifies replies on the phone, and updates the CRM without anyone copy-pasting notes.
See the stack