Gmail and Google Docs for OpenClaw, with guardrails
OpenClaw gets your inbox, documents and spreadsheets through one hosted MCP server. No Google Cloud project, no client secrets on the box. You decide what it can read, who it can email and which files it can touch.
Set up OpenClaw in 3 steps
- 1
Add FGAC as an MCP server
One command. Keep--transport streamable-http: OpenClaw defaults to SSE otherwise.openclaw mcp add fgac --url https://fgac.ai/api/mcp --transport streamable-http --auth oauth - 2
Sign in
OpenClaw prints a sign-in link: open it and sign in to FGAC with the Google account you want the agent to use. Finish within about two minutes; if it times out, run the command again. Running OpenClaw on a server? Use the--codefallback the command prints.openclaw mcp login fgac - 3
Start using it
Ask OpenClaw to “summarize my unread email from today”. It starts read-only. Open your FGAC dashboard to let it send, edit, or see more, and to hide mail it shouldn't read.
Several people on one OpenClaw gateway? Set oauth.identity: "per-requester" on the fgac server so each person connects their own account under their own rules. Using Hermes instead? See the Hermes guide.
Why not a full-access Google skill?
The popular Google Workspace skills hand OpenClaw your whole account. That's a lot to trust to an always-on agent that reads untrusted email all day: one injected instruction is enough to forward your inbox somewhere else.
| What OpenClaw gets | Full-access skill | FGAC |
|---|---|---|
| Reads, drafts, and edits your Gmail, Docs, and Sheets | ||
| Hides 2FA codes, password resets, and mail you mark sensitive | ||
| Sends only to recipients you whitelisted | ||
| Sees only the files you exposed, not your whole Drive | ||
| Asks you with a one-click approval link instead of failing | ||
| Your Google token never sits on the agent's machine | ||
| Revoke the agent in one click without touching Google |
See every setup option
Free for personal use · full documentation