Permite que un cliente de IA lea, busque, organice, redacte y envíe mensajes y conversaciones de Gmail.
También conocido como pulsemcp/mcp-servers, gmail-workspace-mcp-server
- Stars
- 81
- Herramientas
- 22
- Descargas, 30 días
- 408
- Última versión
- 0.4.12
- Último commit
- 9 oct 2026
- Licencia
- MIT
¿Qué es Gmail MCP?
Permite que un cliente de IA lea, busque, organice, redacte y envíe mensajes y conversaciones de Gmail. Expone 22 herramientas, como readonly, readwrite, readwrite_external.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Gmail
Gestionar las comunicaciones por correo electrónico mediante un asistente de IA es posible con esta integración de Gmail. Permite a los usuarios buscar, leer, organizar y redactar mensajes directamente desde su cliente. El servidor es compatible tanto con cuentas personales de Gmail mediante credenciales OAuth2 como con entornos de Google Workspace a través de cuentas de servicio con delegación de dominio.
Los desarrolladores pueden controlar el nivel de acceso habilitando grupos de herramientas específicos. El grupo readonly permite buscar y listar conversaciones, mientras que el grupo readwrite añade la capacidad de modificar etiquetas y gestionar borradores. El grupo readwrite_external proporciona el nivel más alto de acceso, incluyendo la capacidad de enviar correos electrónicos. Este sistema de permisos granulares ayuda a gestionar los riesgos asociados con las acciones de correo automatizadas.
La configuración requiere configurar variables de entorno como client IDs, secrets o claves JSON de cuentas de servicio. Una vez conectado, el asistente puede realizar tareas como marcar mensajes como leídos, marcar hilos con estrella o redactar respuestas utilizando la sintaxis de consulta nativa de Gmail.
Qué puedes hacer con él
- 1Organizar la bandeja de entradaArchivar automáticamente mensajes antiguos o aplicar etiquetas específicas al correo entrante.
- 2Redactar respuestas de correoCrear nuevos borradores de correo como respuestas a hilos de conversación existentes.
- 3Enviar correo salienteEnviar mensajes nuevos o despachar borradores existentes a los destinatarios.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Gmail MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Gmail MCP en Claude Code
$ claude mcp add --env 'GMAIL_OAUTH_CLIENT_ID=<YOUR_GMAIL_OAUTH_CLIENT_ID>' --env 'GMAIL_OAUTH_CLIENT_SECRET=<YOUR_GMAIL_OAUTH_CLIENT_SECRET>' --env 'GMAIL_OAUTH_REFRESH_TOKEN=<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>' --env 'GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY=<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>' gmail -- npx -y gmail-workspace-mcp-serverInstalar Gmail MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server"
],
"env": {
"GMAIL_OAUTH_CLIENT_ID": "<YOUR_GMAIL_OAUTH_CLIENT_ID>",
"GMAIL_OAUTH_CLIENT_SECRET": "<YOUR_GMAIL_OAUTH_CLIENT_SECRET>",
"GMAIL_OAUTH_REFRESH_TOKEN": "<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>",
"GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY": "<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}Instalar Gmail MCP en VS Code
.vscode/mcp.json
{
"servers": {
"gmail": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server"
],
"env": {
"GMAIL_OAUTH_CLIENT_ID": "<YOUR_GMAIL_OAUTH_CLIENT_ID>",
"GMAIL_OAUTH_CLIENT_SECRET": "<YOUR_GMAIL_OAUTH_CLIENT_SECRET>",
"GMAIL_OAUTH_REFRESH_TOKEN": "<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>",
"GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY": "<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}Instalar Gmail MCP en VS Code CLI
$ code --add-mcp '{"name":"gmail","type":"stdio","command":"npx","args":["-y","gmail-workspace-mcp-server"],"env":{"GMAIL_OAUTH_CLIENT_ID":"<YOUR_GMAIL_OAUTH_CLIENT_ID>","GMAIL_OAUTH_CLIENT_SECRET":"<YOUR_GMAIL_OAUTH_CLIENT_SECRET>","GMAIL_OAUTH_REFRESH_TOKEN":"<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>","GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY":"<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"}}'Instalar Gmail MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server"
],
"env": {
"GMAIL_OAUTH_CLIENT_ID": "<YOUR_GMAIL_OAUTH_CLIENT_ID>",
"GMAIL_OAUTH_CLIENT_SECRET": "<YOUR_GMAIL_OAUTH_CLIENT_SECRET>",
"GMAIL_OAUTH_REFRESH_TOKEN": "<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>",
"GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY": "<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}Instalar Gmail MCP en Codex
$ codex mcp add gmail --env 'GMAIL_OAUTH_CLIENT_ID=<YOUR_GMAIL_OAUTH_CLIENT_ID>' --env 'GMAIL_OAUTH_CLIENT_SECRET=<YOUR_GMAIL_OAUTH_CLIENT_SECRET>' --env 'GMAIL_OAUTH_REFRESH_TOKEN=<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>' --env 'GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY=<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>' -- npx -y gmail-workspace-mcp-serverInstalar Gmail MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.gmail] command = "npx" args = ["-y", "gmail-workspace-mcp-server"] [mcp_servers.gmail.env] GMAIL_OAUTH_CLIENT_ID = "<YOUR_GMAIL_OAUTH_CLIENT_ID>" GMAIL_OAUTH_CLIENT_SECRET = "<YOUR_GMAIL_OAUTH_CLIENT_SECRET>" GMAIL_OAUTH_REFRESH_TOKEN = "<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>" GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY = "<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"
Instalar Gmail MCP en Gemini CLI
$ gemini mcp add -s user -e 'GMAIL_OAUTH_CLIENT_ID=<YOUR_GMAIL_OAUTH_CLIENT_ID>' -e 'GMAIL_OAUTH_CLIENT_SECRET=<YOUR_GMAIL_OAUTH_CLIENT_SECRET>' -e 'GMAIL_OAUTH_REFRESH_TOKEN=<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>' -e 'GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY=<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>' gmail npx -- -y gmail-workspace-mcp-serverInstalar Gmail MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": [
"-y",
"gmail-workspace-mcp-server"
],
"env": {
"GMAIL_OAUTH_CLIENT_ID": "<YOUR_GMAIL_OAUTH_CLIENT_ID>",
"GMAIL_OAUTH_CLIENT_SECRET": "<YOUR_GMAIL_OAUTH_CLIENT_SECRET>",
"GMAIL_OAUTH_REFRESH_TOKEN": "<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>",
"GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY": "<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}Necesita una clave para iniciar
Iniciado el 16 nov 2026 sin claves, se detuvo y pidió una, así que un cliente no ve herramientas hasta que configures las variables de arriba.
Herramientas de Gmail MCP 22
Detectado desde el READMEreadonlyreadwritereadwrite_externalcountlabelssort_byafterbeforeemail_idquerystatusis_starred
| readonly | — | |
| readwrite | — | |
| readwrite_external | — | |
| count | — | |
| labels | — | |
| sort_by | — | |
| after | — | |
| before | — | |
| email_id | — | |
| query | — | |
| status | — | |
| is_starred | — |
Mostrar las 22 herramientasMostrar menos herramientas
remove_labelsthread_iddraft_iddeletesubjectplaintext_bodyhtml_bodybccreply_to_email_idfrom_draft_id
| remove_labels | — | |
| thread_id | — | |
| draft_id | — | |
| delete | — | |
| subject | — | |
| plaintext_body | — | |
| html_body | — | |
| bcc | — | |
| reply_to_email_id | — | |
| from_draft_id | — |
Configuración
GMAIL_OAUTH_CLIENT_IDSecretoOAuth2 client ID from Google Cloud Console (for personal Gmail accounts).
GMAIL_OAUTH_CLIENT_SECRETSecretoOAuth2 client secret from Google Cloud Console.
GMAIL_OAUTH_REFRESH_TOKENSecretoRefresh token from the OAuth2 setup script.
GMAIL_SERVICE_ACCOUNT_PRIVATE_KEYSecretoService account private key in PEM format (for Google Workspace).
GMAIL_ENABLED_TOOLGROUPSComma-separated list of tool groups to enable (readonly, readwrite, readwrite_external).
GMAIL_IMPERSONATE_EMAILEmail address to impersonate (required for service account mode).
GMAIL_SERVICE_ACCOUNT_CLIENT_EMAILService account email address (for Google Workspace).
| Nombre | Descripción | Tipo |
|---|---|---|
| GMAIL_OAUTH_CLIENT_ID | OAuth2 client ID from Google Cloud Console (for personal Gmail accounts). | Secreto |
| GMAIL_OAUTH_CLIENT_SECRET | OAuth2 client secret from Google Cloud Console. | Secreto |
| GMAIL_OAUTH_REFRESH_TOKEN | Refresh token from the OAuth2 setup script. | Secreto |
| GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY | Service account private key in PEM format (for Google Workspace). | Secreto |
| GMAIL_ENABLED_TOOLGROUPS | Comma-separated list of tool groups to enable (readonly, readwrite, readwrite_external). | |
| GMAIL_IMPERSONATE_EMAIL | Email address to impersonate (required for service account mode). | |
| GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL | Service account email address (for Google Workspace). |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularAprobado
- El endpoint remoto usa HTTPSNo verificado
- Las herramientas destructivas están etiquetadasNo verificado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasAprobado
README
Ver en GitHubGmail Workspace MCP Server
An MCP (Model Context Protocol) server that provides Gmail integration for AI assistants. Supports both personal Gmail accounts (via OAuth2) and Google Workspace accounts (via service account with domain-wide delegation).
Features
- List Email Conversations: Retrieve emails with label filtering
- Get Email Details: Fetch full email content including body and attachments info
- Search Emails: Search using Gmail's powerful query syntax
- Manage Emails: Mark as read/unread, star/unstar, archive, apply labels
- Create Drafts: Compose draft emails with reply support
- Send Emails: Send new emails or replies, directly or from drafts
- Two Auth Methods: OAuth2 for personal accounts, Service Account for Google Workspace
Installation
npm install gmail-workspace-mcp-server
Or run directly with npx:
npx gmail-workspace-mcp-server
Authentication
This server supports two authentication modes. Choose the one that matches your account type.
Option 1: OAuth2 (Personal Gmail Accounts)
Use this for personal @gmail.com accounts or any Google account without Workspace admin access.
Prerequisites
- Go to Google Cloud Console
- Create or select a project
- Enable the Gmail API
- Configure the OAuth consent screen:
- Choose External user type
- Add yourself as a test user
- Publish the app (click "Publish" on the consent screen) to prevent refresh tokens from expiring every 7 days. No full Google verification is needed for personal use.
- Create OAuth 2.0 credentials:
- Choose Desktop app as the application type
- Important: Create new credentials after publishing the app
- Copy the Client ID and Client Secret
Getting a Refresh Token
Run the built-in setup command:
npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>
You can also pass credentials via environment variables:
GMAIL_OAUTH_CLIENT_ID=... GMAIL_OAUTH_CLIENT_SECRET=... npx gmail-workspace-mcp-server oauth-setup
Port conflict? If port 3000 is already in use, specify a different port:
PORT=3001 npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>
Desktop app credentials automatically allow http://localhost redirects on any port, so no additional Google Cloud Console configuration is needed.
This will open your browser for Google sign-in and print the refresh token. You only need to do this once — the refresh token does not expire (as long as the OAuth consent screen is published).
Environment Variables (OAuth2)
| Variable | Required | Description |
|---|---|---|
GMAIL_OAUTH_CLIENT_ID |
Yes | OAuth2 client ID from Google Cloud Console |
GMAIL_OAUTH_CLIENT_SECRET |
Yes | OAuth2 client secret |
GMAIL_OAUTH_REFRESH_TOKEN |
Yes | Refresh token from the setup script |
GMAIL_ENABLED_TOOLGROUPS |
No | Comma-separated list of tool groups (default: all) |
Claude Desktop Configuration (OAuth2)
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["gmail-workspace-mcp-server"],
"env": {
"GMAIL_OAUTH_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
"GMAIL_OAUTH_CLIENT_SECRET": "your-client-secret",
"GMAIL_OAUTH_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Option 2: Service Account (Google Workspace)
Use this for Google Workspace organizations where a domain admin can grant domain-wide delegation.
Prerequisites
- Go to Google Cloud Console
- Create or select a project
- Enable the Gmail API
- Create a service account with domain-wide delegation enabled
- In Google Workspace Admin Console, grant the service account access to the following scopes:
https://www.googleapis.com/auth/gmail.readonly(read emails)https://www.googleapis.com/auth/gmail.modify(modify labels)https://www.googleapis.com/auth/gmail.compose(create drafts)https://www.googleapis.com/auth/gmail.send(send emails)
- Download the JSON key file
Environment Variables (Service Account)
| Variable | Required | Description |
|---|---|---|
GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL |
Yes | Service account email address |
GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY |
Yes | Service account private key (PEM format) |
GMAIL_IMPERSONATE_EMAIL |
Yes | Email address to impersonate |
GMAIL_ENABLED_TOOLGROUPS |
No | Comma-separated list of tool groups to enable (default: all groups) |
You can find the client_email and private_key values in your service account JSON key file.
Claude Desktop Configuration (Service Account)
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["gmail-workspace-mcp-server"],
"env": {
"GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL": "my-service-account@my-project.iam.gserviceaccount.com",
"GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY": "-----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----",
"GMAIL_IMPERSONATE_EMAIL": "user@yourdomain.com"
}
}
}
}
Note: For the private key, you can either:
- Use the key directly with
\nfor newlines (as shown above) - Set the environment variable from a shell that preserves newlines
Tool Groups
The server supports three tool groups for permission-based access control:
| Group | Tools Included | Risk Level |
|---|---|---|
readonly |
list_email_conversations, get_email_conversation, search_email_conversations, list_draft_emails |
Low |
readwrite |
All readonly tools + change_email_conversation, upsert_draft_email |
Medium |
readwrite_external |
All readwrite tools + send_email |
High |
By default, all tool groups are enabled. To restrict access, set the GMAIL_ENABLED_TOOLGROUPS environment variable:
# Read-only access (no write/send capabilities)
GMAIL_ENABLED_TOOLGROUPS=readonly
# Read and write, but no external sending
GMAIL_ENABLED_TOOLGROUPS=readwrite
# Full access including sending emails (default)
GMAIL_ENABLED_TOOLGROUPS=readwrite_external
Security Note: The send_email tool is in a separate readwrite_external group because it can send emails externally, which carries higher risk than internal operations like modifying labels or creating drafts.
Available Tools
list_email_conversations
List email conversations from Gmail with optional filtering.
Parameters:
count(number, optional): Number of emails to return (default: 10, max: 100)labels(string, optional): Comma-separated label IDs to filter by (default: "INBOX")sort_by(string, optional): Sort order - "recent" (newest first) or "oldest" (default: recent)after(string, optional): Only return emails after this datetime, exclusive (ISO 8601 UTC, e.g., "2024-01-15T14:30:00Z")before(string, optional): Only return emails before this datetime, exclusive (ISO 8601 UTC, e.g., "2024-01-15T14:30:00Z")
Example:
{
"count": 20,
"labels": "INBOX,STARRED",
"after": "2024-01-15T00:00:00Z",
"before": "2024-01-20T23:59:59Z"
}
get_email_conversation
Retrieve the full content of a specific email by its ID.
Parameters:
email_id(string, required): The unique identifier of the email
Example:
{
"email_id": "18abc123def456"
}
search_email_conversations
Search emails using Gmail's powerful query syntax.
Parameters:
query(string, required): Gmail search query (e.g., "from:user@example.com", "is:unread", "subject:meeting")count(number, optional): Maximum results to return (default: 10, max: 100)
Example:
{
"query": "from:alice@example.com is:unread",
"count": 20
}
change_email_conversation
Modify email labels and status (read/unread, starred, archived).
Parameters:
email_id(string, required): The email ID to modifystatus(string, optional): "read", "unread", or "archived"is_starred(boolean, optional): Star or unstar the emaillabels(string, optional): Comma-separated labels to addremove_labels(string, optional): Comma-separated labels to remove
Example:
{
"email_id": "18abc123def456",
"status": "read",
"is_starred": true
}
list_draft_emails
List draft emails from Gmail with optional thread filtering.
Parameters:
count(number, optional): Maximum number of drafts to return (default: 10, max: 100)thread_id(string, optional): Filter drafts by conversation thread ID
Example:
{
"thread_id": "18abc123def456"
}
upsert_draft_email
Create, update, or delete a draft email. Optionally as a reply to an existing conversation.
Parameters:
draft_id(string, optional): ID of an existing draft to update or delete (omit to create a new draft)delete(boolean, optional): Set totrueto delete the draft specified bydraft_id. All other parameters are ignored when deletingto(string, required for create/update): Recipient email addresssubject(string, required for create/update): Email subjectplaintext_body(string): Plain text body content (at least one of plaintext_body or html_body required for create/update)html_body(string): HTML body content for rich text formatting (at least one of plaintext_body or html_body required for create/update)cc(string, optional): CC recipientsbcc(string, optional): BCC recipientsthread_id(string, optional): Thread ID for repliesreply_to_email_id(string, optional): Email ID to reply to (sets References/In-Reply-To headers)
For create/update: at least one of plaintext_body or html_body must be provided. If both are provided, a multipart email is sent with both versions.
Example (create new draft):
{
"to": "recipient@example.com",
"subject": "Meeting Follow-up",
"plaintext_body": "Thanks for the meeting today!"
}
Example (update existing draft):
{
"draft_id": "r123456789",
"to": "recipient@example.com",
"subject": "Meeting Follow-up (revised)",
"html_body": "<p>Thanks for the meeting today! Check out <a href=\"https://example.com/notes\">the notes</a>.</p>"
}
Example (delete a draft):
{
"draft_id": "r123456789",
"delete": true
}
send_email
Send an email directly or from an existing draft.
Parameters:
to(string, conditional): Recipient email (required unless sending from draft)subject(string, conditional): Email subject (required unless sending from draft)plaintext_body(string): Plain text body content (at least one of plaintext_body or html_body required, unless sending a draft)html_body(string): HTML body content for rich text formatting (at least one of plaintext_body or html_body required, unless sending a draft)cc(string, optional): CC recipientsbcc(string, optional): BCC recipientsfrom_draft_id(string, optional): Send an existing draft by IDthread_id(string, optional): Thread ID for repliesreply_to_email_id(string, optional): Email ID to reply to
Example (plain text email):
{
"to": "recipient@example.com",
"subject": "Hello",
"plaintext_body": "This is a test email."
}
Example (HTML email):
{
"to": "recipient@example.com",
"subject": "Hello",
"html_body": "<p>Check out <a href=\"https://example.com\">our website</a> for more details.</p>"
}
Example (send draft):
{
"from_draft_id": "r123456789"
}
Development
Setup
# Install dependencies
npm run install-all
# Build
npm run build
# Run in development mode
npm run dev
Testing
# Run functional tests
npm test
# Run integration tests
npm run test:integration
# Run manual tests (requires credentials)
npm run test:manual
License
MIT
Preguntas sobre Gmail MCP
¿Cómo agrego Gmail MCP a Claude Code?
Ejecuta claude mcp add --env 'GMAIL_OAUTH_CLIENT_ID=<YOUR_GMAIL_OAUTH_CLIENT_ID>' --env 'GMAIL_OAUTH_CLIENT_SECRET=<YOUR_GMAIL_OAUTH_CLIENT_SECRET>' --env 'GMAIL_OAUTH_REFRESH_TOKEN=<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>' --env 'GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY=<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>' gmail -- npx -y gmail-workspace-mcp-server en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Gmail MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona Gmail MCP?
Expone 22 herramientas, incluidas readonly, readwrite, readwrite_external, count, labels.
¿Cómo se autentica el Gmail MCP server?
Soporta OAuth2 para cuentas personales de Gmail y una cuenta de servicio con delegación de dominio para cuentas de Google Workspace.
¿Puede el Gmail MCP server buscar en mi bandeja de entrada?
Sí, busca correos electrónicos utilizando la sintaxis de consulta de Gmail, como from:usuario@ejemplo.com o is:unread.
¿Puedo limitar el Gmail MCP server a acceso de solo lectura?
Sí, establece la variable de entorno GMAIL_ENABLED_TOOLGROUPS en readonly para desactivar las herramientas de escritura y envío.
¿Puede el Gmail MCP server enviar correos electrónicos?
Sí, la herramienta send_email envía correos nuevos o respuestas, ya sea directamente o desde un borrador existente.
¿Cómo obtengo un token de actualización de OAuth2 para Gmail?
Ejecuta el comando integrado oauth-setup con tu client ID y secret, y luego inicia sesión a través del navegador.