Google Workspace Gmail MCP server
Automate email workflows and let an AI agent manage inbox tasks, draft responses, and organize messages. This MCP server enables reading, sending, labeling, and searching emails—ideal for support ticket triage, customer email summarization, and inbox automation.
Setting up an MCP server
This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the Authentication section on this page.
Before you begin
You'll need:
- Access to AI Gateway with permission to create MCP servers.
- API credentials for the application you're connecting (see the Authentication section on this page for what to collect).
Create an MCP server
Find the app in the catalog
- Sign in to AI Gateway and select App Catalog from the left navigation.
- Search for the application you want to connect, then select it from the catalog.
- Select Create MCP Server to start the wizard.
App Configuration
Confirm the Base URL for the API, then, under Tools, select the endpoints you want to expose. Select Next.
MCP Server Setup
- Enter a Name for your server — something descriptive that identifies both the application and its purpose.
- Enter a Description so your team knows what the server is for.
- Set the log level: choose Production Mode for terser logs, or Non-Production Mode for more verbose logs that can help with debugging.
- Select Next.
Authentication
Enter the authentication details for the application. This varies by service — see the Authentication section on this page for the specific credentials, OAuth URLs, and scopes to use.
Review
Look over the summary of your MCP server configuration, then select Create & Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.
Connect to an AI client
Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:
Tips
- You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
- If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
Authentication
Gmail API uses OAuth 2.0 with scope-based permissions. Set up OAuth credentials in Google Cloud Console, specifying the application type as "Web application". In Google Cloud Console, go to APIs & Services > Credentials and create a Web application OAuth 2.0 credential.
| Value | Setting |
|---|---|
| Redirect URI | https://auth.aigateway.cequence.ai/v1/outbound/oauth/callback |
| Auth endpoint | https://accounts.google.com/o/oauth2/auth |
| Token endpoint | https://oauth2.googleapis.com/token |
| Scopes | https://www.googleapis.com/auth/gmail.readonly, https://www.googleapis.com/auth/gmail.compose, https://www.googleapis.com/auth/gmail.send, https://www.googleapis.com/auth/gmail.modify, https://mail.google.com/ |
Available tools
These tools enable email management, composition, organization, and analysis.
| Tool | Description |
|---|---|
| Get message | Retrieve a specific email with headers and content |
| List messages | Query emails by label, sender, or search criteria |
| Send message | Compose and send a new email |
| Create draft | Write an email without sending |
| Update draft | Modify a draft before sending |
| Modify message | Change labels, mark as read/unread, or archive |
| Delete message | Move email to trash or permanently delete |
| Create label | Create a new label for organizing emails |
| Manage labels | Apply, remove, or modify email labels |
| Search emails | Find emails using Gmail search syntax |
| Get thread | Retrieve an entire email conversation |
| Add attachment | Include files in email messages |
| Get attachment | Download an attachment from an email |
Tips
Start with gmail.readonly and gmail.send scopes for most automation tasks—this prevents accidental deletion while still enabling sending and reading.
Combine email search with label automation to triage incoming mail without manual action for support ticket workflows.
Validate sender addresses and use allowlists for auto-reply or forwarding rules to prevent accidentally responding to spoofed emails.
Include a disclaimer or signature that makes it clear the message was AI-generated when drafting responses, so recipients know they may need human review for sensitive issues.
Implement rate limiting in your automation (Gmail allows 250 quota units per user per second) and monitor quota usage in Google Cloud Console to avoid hitting limits during peak email volume.
Cequence AI Gateway