Open-source LLM knowledge base: team chat into a typed knowledge graph and auto-generated wiki.
Open-source LLM knowledge base: team chat into a typed knowledge graph and auto-generated wiki. Exposed over MCP by the beever mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
Key — PurposeGOOGLE_API_KEY — Gemini — extraction, entity graph, answersJINA_API_KEY — Jina v4 embeddings (2048-dim) for semantic searchTAVILY_API_KEY — External web search when QA retrieval confidence is low — tavily.comOLOSTEP_API_KEY — Olostep web search (alternative to Tavily). Set WEB_SEARCH_PROVIDER=olostep in your .env — olostep.com/dashboardService — PortBackend — :8000Bot — :3001Weaviate — :8080Neo4j — :7474 / :7687MongoDB — :27017Redis — :6380Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 8 environment variables: GOOGLE_API_KEY, JINA_API_KEY, TAVILY_API_KEY, OLOSTEP_API_KEY, CREDENTIAL_MASTER_KEY, WEAVIATE_API_KEY, BEEVER_LLM_API_KEY, VITE_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Beever's toolset — Key, GOOGLE_API_KEY, JINA_API_KEY and 9 more — is a fair guide to whether it matches your workflow. It is maintained by Beever-AI; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Beever's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Key | Purpose |
| GOOGLE_API_KEY | Gemini — extraction, entity graph, answers |
| JINA_API_KEY | Jina v4 embeddings (2048-dim) for semantic search |
| TAVILY_API_KEY | External web search when QA retrieval confidence is low — [tavily.com](https://tavily.com/) |
| OLOSTEP_API_KEY | Olostep web search (alternative to Tavily). Set WEB_SEARCH_PROVIDER=olostep in your .env — [olostep.com/dashboard](https://www.olostep.com/dashboard) |
| Service | Port |
| Backend | :8000 |
| Bot | :3001 |
| Weaviate | :8080 |
| Neo4j | :7474 / :7687 |
| MongoDB | :27017 |
| Redis | :6380 |
{
"mcpServers": {
"beever-atlas": {
"url": "https://atlas.example.com/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer ${BEEVER_MCP_KEY}"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_API_KEY | Credential the server authenticates with. | Yes |
| JINA_API_KEY | Credential the server authenticates with. | Yes |
| TAVILY_API_KEY | Credential the server authenticates with. | Yes |
| OLOSTEP_API_KEY | Credential the server authenticates with. | Yes |
| CREDENTIAL_MASTER_KEY | Credential the server authenticates with. | Yes |
| WEAVIATE_API_KEY | Credential the server authenticates with. | Yes |
| BEEVER_LLM_API_KEY | Credential the server authenticates with. | Yes |
| VITE_API_URL | Endpoint or connection string the server talks to. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.