Beever Atlas
OfficialRelated Servers
Alternatives to Beever Atlas
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnd-to-end agent-managed company brain. Humans and any MCP agent co-author living docs (Markdown + extensions), 40+ visual diagrams (Mermaid, BPMN, D2, PlantUML, ELK, Excalidraw), plans, and a self-learning Knowledge Graph. 163 tools across 16 categories. Auth: OAuth 2.1 or API key. Lean, secure, affordable — from individuals to enterprise.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read and write into a self-hosted personal knowledge base built from imported chats, documents, and notes, with a knowledge graph and AI-powered enrichment.1MIT
- AlicenseAqualityAmaintenanceEnables teams to capture and distill knowledge from sessions, meetings, and feeds into a searchable, vector-embedded graph, then retrieve or synthesize it conversationally via semantic search and citations.1724Apache 2.0
- AlicenseNot gradedqualityDmaintenancePersistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.13 npm8MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server for storing and serving structured team knowledge, enabling AI sessions to load relevant team context without re-prompting.Apache 2.0
- AlicenseAqualityCmaintenanceA knowledge base MCP server that aggregates team knowledge from multiple sources into Postgres. It provides hybrid search (full-text + vector + RRF) via MCP tools, and enables direct recording of decisions, learnings, and pitfalls.151MIT
TDQS
Scored across 28 tools
Each tool has a clearly distinct purpose, with descriptions that explicitly contrast similar tools (e.g., find_facts vs. search_channel_facts vs. ask_channel, or read_wiki_page vs. read_wiki_module). Overlapping functionality is minimal and well-documented.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_channels, find_facts, read_provenance). There is no mixing of naming conventions, making the set predictable.
28 tools is on the higher end but appropriate for the server's complex domain (knowledge management with multiple search modes, wiki operations, decision tracking, etc.). The count feels slightly heavy but each tool earns its place.
The tool set covers the full lifecycle: channel discovery, multiple retrieval methods, wiki management (both legacy and redesigned), decision history, tensions, experts, media search, relationship graphs, job tracking, and sync. Obvious gaps (e.g., fact deletion) are intentionally omitted as read-only. The deprecated tool is a minor blemish.