MCP Catalogs
Homebeever-atlas screenshot

beever-atlas

by Beever-AI·328·Score 50

Beever Atlas is an MCP server that transforms team chats into a self-maintaining wiki with integrated search and QA capabilities.

communicationknowledge-graphai-llm
40
Forks
3
Open issues
this month
Last commit
2d ago
Indexed

Overview

Beever Atlas extracts atomic facts from Slack, Discord, Teams, and Mattermost conversations, deduplicates and clusters them into topic pages with citations. It features a 3-tier semantic store and graph memory system that fuels both an auto-generated LLM wiki and a QA agent accessible through the dashboard or MCP integration. The system supports 16 MCP tools for querying knowledge bases with per-agent authentication capabilities.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Automatically team documentation from chat conversations
you:AI-powered search across team communications with source citations
you:Integrate team knowledge base into Claude Code and Cursor via MCP
you:What platforms does Beever Atlas support?
you:How many MCP tools does Beever Atlas provide?

When to choose this

Choose Beever Atlas if your team already uses Slack/Discord/Teams and wants to automatically transform conversations into a structured knowledge base accessible via MCP for AI agents.

When NOT to choose this

Avoid Beever Atlas if you need full control over data storage (it uses Weaviate, Neo4j, MongoDB, Redis), require a self-hosted solution without cloud dependencies, or need to process documents outside of team chat platforms.

Tools this server exposes

12 tools extracted from the README
  • ask_knowledge_base

    Ask questions about the knowledge base and get cited answers.

  • get_channel_wiki

    Retrieve the auto-generated wiki for a specific channel.

  • search_messages

    Search for specific messages or conversations across all connected platforms.

  • get_entity_graph

    Retrieve the entity graph showing relationships between people, projects, and decisions.

  • list_topics

    List all identified topics in a channel's knowledge base.

  • get_topic_details

    Get detailed information about a specific topic including citations.

  • get_citations

    Retrieve source citations for a specific fact or answer.

  • get_people_mentions

    Find all mentions of specific people across conversations.

  • get_project_timeline

    Retrieve the timeline of events and decisions for a specific project.

  • get_channel_overview

    Get a high-level overview of a channel's activity and key topics.

  • get_faq

    Retrieve frequently asked questions and answers for a channel.

  • get_glossary

    Access the glossary of terms and their definitions from a channel.

Note: Inferred from the MCP server feature description and architecture diagram, which mentions '16 tools' but doesn't list them explicitly. Tool names and descriptions are based on the functionality described in the README about the knowledge ba

Comparable tools

semantic-search-mcpchat-to-docs-mcpdiscord-ai-mcpslack-ai-mcp

Installation

Installation

  1. Clone the repository:
git clone https://github.com/beever-ai/beever-atlas.git
cd beever-atlas
  1. Try the demo (optional):
make demo
  1. Get API keys:
  • GOOGLE_API_KEY for Gemini extraction and answers
  • JINA_API_KEY for embeddings (Jina v4)
  1. Install with one line:
./atlas

This will walk you through setup including embedding model, LLM provider, graph backend, and MCP server configuration.

Claude Desktop Integration

Add to Claude Desktop config:

{
  "mcpServers": {
    "beever-atlas": {
      "command": "npx",
      "args": ["beever-atlas-mcp"]
    }
  }
}

FAQ

What platforms does Beever Atlas support?
Beever Atlas supports Slack, Discord, Microsoft Teams, and Mattermost conversations. It can also import from files.
How many MCP tools does Beever Atlas provide?
Beever Atlas provides 16 MCP tools for querying the knowledge base with per-agent authentication capabilities.

Compare beever-atlas with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.