How we picked LibreChat — and ended up with a Slack agent
metabase.com | blog | #ai-security | #cloud | #mcp | #metabase | #slack | #self-hosted | #librechat | #ai-tooling
Summary
Metabase's Cloud team explains consolidating scattered AI logins behind self-hosted LibreChat — chosen for operability and MCP support — and building LibreBot, the Slack agent that runs on top of it.
- Published
- Collected
--- id: 6372 title: "How we picked LibreChat — and ended up with a Slack agent" source_domain: metabase.com source_url: "https://www.metabase.com/blog/librechat-self-hosted" published_at: "2026-07-20T00:00:00Z" tags: ["ai-security", "cloud", "mcp", "metabase", "slack", "self-hosted", "librechat", "ai-tooling"] phying_url: "https://phying.com/item/6372" lang: en --- # How we picked LibreChat — and ended up with a Slack agent ## Summary Metabase's Cloud team explains consolidating scattered AI logins behind self-hosted LibreChat — chosen for operability and MCP support — and building LibreBot, the Slack agent that runs on top of it. ## Intelligence Metadata - **Sources:** metabase.com - **Published:** 2026-07-20T00:00:00Z - **Original:** https://www.metabase.com/blog/librechat-self-hosted - **Phying News:** https://phying.com/item/6372