[ MCP SERVER SUMMARY ]
Gmail MCP server summary
Gmail's remote MCP server (Developer Preview) lets AI agents search threads, manage labels, and create drafts under the user's Google permissions. Bifrost registers the HTTP endpoint with OAuth so Workspace email tools are governed, logged, and scoped per virtual key.
| Property | Details |
|---|---|
| Company | |
| Connection type | HTTP |
| Authentication | OAuth 2.0 (Google Cloud client) |
| Package or endpoint | https://gmailmcp.googleapis.com/mcp/v1 |
| Capabilities | Search threads and messages, Create drafts, Label management |
| Official documentation | Gmail MCP documentation |
Before you start
- Google Cloud project with Gmail API and Gmail MCP API enabled
- OAuth client ID/secret and consent screen configured
What you can do with Gmail
- Let support agents draft replies without embedding Gmail OAuth in every laptop
- Restrict compose tools while allowing search for research assistants
- Meet audit requirements for AI access to mailbox data
[ HOW TO CONNECT ]
Connect Gmail to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Gmail in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Enable gmail.googleapis.com and gmailmcp.googleapis.com in GCP.
• Developer Preview — enroll via Google Workspace Developer Preview Program if required.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Gmail.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Gmail via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "gmail",
"connection_type": "http",
"connection_string": "https://gmailmcp.googleapis.com/mcp/v1",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Gmail through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Gmail MCP server do?
Gmail exposes search threads and messages, create drafts, label management to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Gmail authenticate when used with Bifrost?
Gmail uses OAuth 2.0 (Google Cloud client). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Gmail through Bifrost?
Yes. After registering Gmail in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Google Calendar
Let AI assistants access Google Calendar events and automate scheduling workflows through Google Workspace MCP.
Google Drive
Connect AI assistants to files and folders in Google Drive through Google Workspace MCP.
Google Chat
Enable AI assistants to work with Google Chat spaces, messages, and collaboration workflows through Google Workspace MCP.