← Back to directory
B

Beever Atlas

Community
Open-source LLM knowledge base that turns team chats into a typed knowledge graph and auto-generated wiki.
GitHub source repository ↗
★ 442 Stars Category · Other Very popular Source revision 7d791af27ef4
47FMRS · D
Reliability
5/20
Security and permissions
10/20
Maintenance
10/20
Documentation
14/20
Setup experience
8/20

Beever Atlas is an innovative LLM knowledge base implementation that improves accuracy and traceability by distilling chat data into structured wikis and knowledge graphs. It offers extensive MCP integration and is suitable for teams needing knowledge management. However, it requires self-hosting, configuration is complex, and API stability is not guaranteed, making it best for technically capable teams.

Read the FMRS scoring method →

Beever Atlas is an open-source LLM knowledge base that connects Slack, Discord, Microsoft Teams, and Mattermost. It extracts atomic facts from messages, deduplicates them, and clusters them into topic pages with citations. Data is stored in a semantic store (Weaviate) and a graph store (Neo4j), enabling relational queries about people, decisions, and projects. Users can query the knowledge base via a dashboard or through MCP, allowing AI agents like Claude Code and Cursor to get cited answers in natural language.

Tools

list_tools
List all available tools on the server.
search_facts
Search atomic facts in the knowledge base.
search_topics
Search topic pages.
get_topic
Get details for a specific topic.
get_channel_wiki
Get the auto-generated wiki for a channel.
get_channel_summary
Get a summary or overview of a channel.
get_graph
Get entity-relationship view of the knowledge graph.
get_relations
Query relations for a specific entity.
get_qa
Ask the Q&A agent a question and get a cited answer.
start_sync
Start a channel sync.
get_sync_status
Get the status of a sync operation.
list_channels
List available channels.
list_workspaces
List connected workspaces.
search_entities
Search entities (people, projects, etc.).
get_entity
Get details for a specific entity.

Setup

  1. Clone the repo and enter: git clone https://github.com/beever-ai/beever-atlas.git && cd beever-atlas.
  2. Optional: run make demo to try the seeded demo (no API keys needed).
  3. Obtain API keys: GOOGLE_API_KEY (Gemini) and JINA_API_KEY (embeddings) are required; optionally TAVILY_API_KEY or OLOSTEP_API_KEY for web search.
  4. Choose deployment: recommended ./atlas interactive installer, or manually copy .env.example and fill in keys, then run docker compose up -d --build.
  5. Open the dashboard (default http://localhost:3000) and configure AI providers in Settings.
  6. Add a workspace (Slack/Discord/Teams) under Connections and sync channels.
  7. For MCP clients, configure .mcp.json with streamable-http or stdio as per docs.
claude_desktop_config.json
{
  "mcpServers": {
    "beever-atlas": {
      "url": "https://atlas.example.com/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer ${BEEVER_MCP_KEY}"
      }
    }
  }
}

Fit and risk

Best for

  • Teams that need to distill large volumes of chat into searchable, citable knowledge.
  • RAG applications that want to improve answer consistency and reduce hallucinations.
  • Developers who want MCP integration to let AI coding assistants access team knowledge.

Not for

  • Lightweight use cases that just need a simple chat log search.
  • Users who cannot self-host Docker-based infrastructure or prefer serverless options.
  • Those needing deep integration with proprietary knowledge management products without self-hosting.

Required permissions

  • Requires read access to Slack, Discord, Teams, or Mattermost channels (bot tokens configured via UI).
  • Access to external APIs: Gemini, Jina Embeddings (required); optional Tavily/Olostep web search.
  • Runtime requires Docker, network ports (3000, 8000, 3001, 8080, 7474, 7687, 27017, 6380).
  • For MCP clients, requires BEEVER_MCP_API_KEYS authentication.

Risks and side effects

  • Indexed chat data may contain sensitive information; ensure data security in deployment.
  • API keys (e.g., Gemini, Jina) if exposed can lead to misuse or data breaches.
  • Auto-generated wiki may contain errors or inaccurate info; human review may be needed.
  • Early-stage version (0.3.0) with unstable API; may break on updates.

Troubleshooting

  1. If containers fail, check `docker compose logs -f beever-atlas` for backend logs.
  2. If sync doesn't work, verify platform credentials are correctly entered in the UI.
  3. If MCP connection fails, check BEEVER_MCP_API_KEYS, URL, and auth headers.
  4. If QA quality is poor, confirm GOOGLE_API_KEY and JINA_API_KEY are valid and models available.
  5. If port conflicts, adjust port settings in .env.

Use cases

Automatically turn team chat history into a structured wiki for onboarding and knowledge sharing.
Let AI agents like Claude Code and Cursor query team knowledge via MCP and get cited answers.
Answer relational questions across channels, such as 'who worked on X with Y?'.
Track decisions, project progress, and personnel in a searchable knowledge base.

Supported clients

ClaudeFull support
CursorFull support