The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the FGAC.ai: Multiple Gmail Accounts, Google Sheets & Docs listing page.
Fine-grain access control for AI agents on Gmail, Google Sheets and Google Docs.
Product: https://fgac.ai · Docs: https://fgac.ai/docs · Privacy: https://fgac.ai/privacy
FGAC.ai is a hosted MCP server and API proxy that sits between your AI agents and your Google accounts. Connect one or many Gmail accounts — work, school, personal, and inboxes teammates delegate to you — plus the specific Google Sheets and Docs you choose, and every request passes through deny-by-default access rules you control before it touches Google. Nothing to install, no Google Cloud project needed: sign in with Google and the agent can read that account's mail immediately; sending, editing, and other inboxes are granted from your dashboard or from a one-click approval link the agent hands you when it is denied.
| Client | How |
|---|---|
| Claude.ai / Claude Desktop | Search FGAC in the connectors directory, or add a custom connector with the URL below |
| Claude Code | claude mcp add --transport http fgac https://fgac.ai/api/mcp |
| VS Code / Copilot, Cursor, Windsurf, Cline | Add a remote MCP server: https://fgac.ai/api/mcp (Streamable HTTP, OAuth sign-in) — or find ai.fgac/fgac in the MCP Registry |
| Smithery | smithery.ai/servers/fgac/fgac |
| Any Google SDK | Point the client's endpoint override at https://fgac.ai/api/proxy with an FGAC proxy key — see the docs |
MCP endpoint: https://fgac.ai/api/mcp (Streamable HTTP; OAuth 2.1 with
dynamic client registration and PKCE; discovery at
/.well-known/oauth-protected-resource/mcp).
Your data is never stored or used for training. See the Terms for service terms.
Two different things, two different terms:
LICENSE for the
exact terms and liability limitations.This is a Next.js app deployed on Vercel, with Clerk for authentication and Neon Postgres via Drizzle. There is exactly one supported way to run it locally, and it depends on access to the project's Vercel environment:
Node 20.9+ is required. npm run env:check diagnoses environment problems.
Contributor rules, QA workflow, and database safety guards are documented in
CLAUDE.md and docs/.