Connected in three steps
Add FGAC as an MCP server, sign in with Google, and decide exactly what your agents can read, write, and send.
Works with any MCP client — one URL everywhere.
Add the MCP server
Pick your client — one click from the directory, or one URL everywhere else.
Claude.ai — web, desktop & mobile
FGAC.ai is listed in the Claude connectors directory — no URLs to paste. Open the listing, click Connect, and jump straight to step 2.
Open FGAC.ai in the Claude directory (opens claude.ai in a new tab)Claude Code
claude mcp add \
--transport http \
fgac https://fgac.ai/api/mcpRun this in any project directory. The server persists across sessions. Working per-project? Each agent profile has its own URL (/api/mcp/<profile>) that maps the connection to that profile automatically — see the per-project guide.
Cursor
Open Settings → MCP Servers. Click Add new HTTP server. Paste the URL above.
Windsurf
Open Settings → MCP. Click Add Server. Choose Streamable HTTP and paste the URL above.
Claude Desktop
Open Settings → Developer → MCP Servers. Add a new server with type "url" and paste the URL above.
FGAC uses MCP Streamable HTTP with OAuth 2.1 (DCR + PKCE). Your client handles authentication automatically.
Sign in — you're connected
Your agent triggers an OAuth flow. Signing in attaches it to your read-only Default Profile.
- AYour agent tries to use a tool — a browser window opens asking you to sign in with Google. This links your agent to your FGAC account. No API keys needed.
- BSafe defaults apply instantly — the agent attaches to your Default Profile: it can read this account's mail, and cannot send, edit, or delete. Upgrade, re-scope, or block it any time in your FGAC Dashboard.
Grant access, service by service
Everything is denied until you allow it. Grants live on reusable agent profiles.
Click + Expose a sheet on a profile and pick files. Each sheet starts read-only; enable write access per sheet when the agent needs it. Full walkthrough with video: let an agent update your Sheets.
Regex rules hide sensitive mail — 2FA codes, password resets, financial alerts. Sending only works to addresses and domains you approve.
Profiles bundle rules and grants into a scoped identity. Your research agent and your inbox agent don't have to share permissions — and each profile has its own MCP URL, so an agent connecting through it lands on the right profile automatically. See per-project profiles in Claude Code.
Multiple Gmail accounts, one agent
One agent connection can reach several inboxes. Other people delegate access from their own FGAC dashboard — no password sharing — and the inbox joins your Default Profile automatically. Your agent then targets it with the account parameter. Every delegation keeps its own rules and is revocable in one click. Step-by-step guide with video: connect multiple Gmail accounts.
Go deeper: use-case guides
Step-by-step walkthroughs — each with a demo video — for the two most common setups.
Let an agent update your Google Sheets
Expose individual spreadsheets, grant read or read & write per sheet, and keep the rest of Drive invisible.
Read the guideGmailMultiple Gmail accounts, one agent
Work + personal inboxes, and mailboxes teammates delegate to you — each under its own rules, revocable in one click.
Read the guideClaude CodeOne profile per project in Claude Code
Scope FGAC to a single project directory and map it to a specific agent profile just by the MCP URL it connects to.
Read the guideAlternative: Direct Proxy Key
For agents that don't support MCP, create a proxy API key and use our downloadable skill files.