What is the key difference between Beever Atlas and Moxie Docs MCP?

Beever Atlas belongs to the Knowledge & Memory category with local stdio execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Beever Atlas or Moxie Docs MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Beever Atlas and Moxie Docs MCP free or paid?

Beever Atlas operates under a BYOK (Pay Provider Direct) model (API Key required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Beever Atlas lists 6 tools with 2 views and 445 GitHub stars. Moxie Docs MCP lists 12 tools with 21 views and 2 GitHub stars.

Can I use both Beever Atlas and Moxie Docs MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Beever Atlas vs Moxie Docs MCP

In-depth architectural comparison of the Beever Atlas and Moxie Docs MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Beever Atlas

Knowledge & Memory · Local stdio

Quality: 52/100 (Good) | Auth: API Key required

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Beever Atlas if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Beever Atlas when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: BEEVER_ATLAS_API_KEY, SLACK_BOT_TOKEN, DISCORD_BOT_TOKEN, TEAMS_APP_ID, TEAMS_APP_PASSWORD, MATTERMOST_ACCESS_TOKEN, LITELLM_API_KEY, MONGODB_URI.
Primary tools included: Multi-platform chat ingestion (Slack, Discord, Teams, Mattermost), Atomic fact extraction and deduplication, Typed knowledge graph linking entities and relationships.

Explore Beever Atlas Details

Choose Moxie Docs MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).

Feature & Specification Comparison

Specification	Beever Atlas Beever-AI Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Open-source LLM knowledge base for teams. 28-tool native MCP server turns Slack/Discord/Teams/Mattermost chat into a typed knowledge graph + auto-generated wiki with cited answers, semantic search, expert finding, and decision tracing. BYO LLM via LiteLLM, Apache 2.0, on-prem via Docker.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Tools & Capabilities Breakdown

Beever Atlas Tools (6)

Multi-platform chat ingestion (Slack, Discord, Teams, Mattermost)

Atomic fact extraction and deduplication

Typed knowledge graph linking entities and relationships

Auto-generated, auto-maintained wiki per channel

Natural language QA with cited source messages

28-tool native MCP server with per-agent authentication

Moxie Docs MCP Tools (12)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Beever Atlas Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "beever-ai-beever-atlas": {
      "command": "npx",
      "args": [
        "-y",
        "beever-ai-beever-atlas"
      ],
      "env": {
        "BEEVER_ATLAS_API_KEY": "YOUR_BEEVER_ATLAS_API_KEY_HERE",
        "SLACK_BOT_TOKEN": "YOUR_SLACK_BOT_TOKEN_HERE",
        "DISCORD_BOT_TOKEN": "YOUR_DISCORD_BOT_TOKEN_HERE",
        "TEAMS_APP_ID": "YOUR_TEAMS_APP_ID_HERE",
        "TEAMS_APP_PASSWORD": "YOUR_TEAMS_APP_PASSWORD_HERE",
        "MATTERMOST_ACCESS_TOKEN": "YOUR_MATTERMOST_ACCESS_TOKEN_HERE",
        "LITELLM_API_KEY": "YOUR_LITELLM_API_KEY_HERE",
        "MONGODB_URI": "YOUR_MONGODB_URI_HERE"
      }
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

Frequently Asked Questions

Beever Atlas is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Beever Atlas when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.

More alternatives to Beever Atlas More alternatives to Moxie Docs MCP Knowledge & Memory category hub