mari

/ connectors · Google Drive

Connect Google Drive to Mari

Google Docs is where half your team's plans, postmortems, and proposals live, findable only by the people who already know they exist. Drive search finds files. It doesn't answer questions, and it can't tell you which of three overlapping docs is the one to trust.

Mari's Google Drive connector brings those docs into a knowledge base with an accountability layer.

What syncs

Connecting, and one honest limitation

The connector takes an OAuth2 access token with the drive.readonly scope (the OAuth playground issues one in a minute). Google's access tokens are short-lived, roughly an hour. Mari's field help says so plainly rather than pretending otherwise: when the token expires, syncs pause until you paste a fresh one. Test connection shows Google's actual error, verbatim. If your Drive knowledge changes weekly, a token refresh when you sync is a small price for read-only scope. If it changes hourly, talk to us about your setup first.

What you get back

Ask a question and the answer streams with numbered citations back to the exact doc. Drive content ranks alongside your repos, Slack threads, and tickets in one hybrid search. And when three overlapping docs disagree, the fact layer settles it: the claim worth trusting gets an owner, a verification state, and a freshness date.

Runs on your infrastructure

Mari is self-hosted and Apache 2.0. Postgres with pgvector is the whole data plane, models run locally through ollama, and every LLM feature has a deterministic fallback. Your docs never leave your deployment.

Start here

Also connects: GitHub, Slack, Confluence, Notion, Jira, and more. 12 connectors, one pipeline.