Developer Preview: The Model Context Protocol (MCP) server for Gmail is now available in developer preview. MCP is an open protocol that enables seamless integration between AI applications and Gmail. By configuring the Gmail MCP server, you enable AI agents to securely read your emails and take actions, such as creating drafts and labeling messages.
For example, you can ask your AI agent: "What did Ariel say in her last email about our marketing plan?"
To get started with the Gmail MCP server, see the following documentation:
To find more available MCP servers, see Model Context Protocol (MCP) servers in Google Workspace.
]]>Generally Available: The Gmail Postmaster Tools API v2 is now generally available. The API provides access to the full Postmaster Tools dataset—including compliance status data—and includes enhancements like flexible querying with queryDomainStats and support for batch operations. For details on how to use the v2 API, see the updated Postmaster Tools API documentation.
Developer Preview: You can now access data in Gmail Postmaster Tools v2 using the v2beta API. The new API provides access to the full Postmaster Tools dataset, including compliance status data.
The v2beta API also includes enhancements such as the queryDomainStats method for
flexible querying, and adds support for batch operations.
To learn how to use the API, see the Postmaster Tools API documentation.
]]>You can now use annotations to create Deal Cards in the Promotions tab. To get started, see the overview of Deal Cards.
]]>For Google Workspace organizations that use hardware key encryption, the Gmail API supports using smart cards for client-side encryption (CSE). For details, see the reference documentation for CseIdentity and CseKeyPair resources.
The messages.import method uses a more performant backend implementation. The new version is API-compatible with the previous implementation and all clients automatically started using the new behavior as of a few weeks ago. The new backend supports parallel message.import calls efficiently and clients can now import messages in parallel for a user to achieve higher migration throughput. The quota cost of the message.import method has been decreased to reflect the new performance.
Deprecated Review Action, which sunsets on July 15th, 2017.
]]>The history.list method supports filtering history records by type.
The messages.batchModify method lets you modify labels on multiple messages by message IDs, in a single batch operation.
The Gmail API supports a gmail.metadata scope. This scope gives developers access to a user's mailbox including history records, labels, and email headers, but not email body's or attachments.
The q request parameter for the drafts.list method restricts results to the messages matching the specified query.
New endpoints for managing mail settings:
]]>The messages.batchDelete method lets you delete multiple messages, by message IDs, in a single batch operation.
The drafts.list method has an includeSpamTrash option, which determines if the response should include drafts with the SPAM or TRASHlabel applied. The default is currently set to true for this option.
To determine the full state of an email before and after a change, the history.list method returns all current Message.labelIds as part of the response in messagesAdded, messagesDeleted, labelsAdded, and labelsRemoved.
Added a Message.internalDate field that exposes the message's creation timestamp in the mailbox.
You can now send push notifications on mailbox updates, providing real-time server notification without the need for constant polling. With Cloud Pub/Sub, you can now use webhooks—for example, to receive callbacks when updates happen. Additionally, you can filter these notifications to specific Gmail labels.
]]>New scopes for labels and inserting messages to better protect users and accommodate apps that don't need full mailbox data access:
https://www.googleapis.com/auth/gmail.insert: Allows the messages.insert and messages.import methods only.https://www.googleapis.com/auth/gmail.labels: Allows all label operations.The messages.insert method now supports the deleted request parameter and lets you set SENT and DRAFT labels.
The history.list method now provides details of the change type in each history record. For example, using the messagesAdded, messagesDeleted, labelsAdded, or labelsDeleted enums, it's possible to easily tell how a message was changed and typically avoids the need for additional calls to synchronize your client.
The messages.import method now supports the following parameters to better support Email Migration use cases:
neverMarkSpamprocessForCalendardeletedYou can now specify message.labelIds on messages.import requests to automatically apply the given labels to the message.
The default behavior no longer automatically adds INBOX and UNREAD labels to messages.import emails. When message.labelIds isn't specified, imported mail is only visible in All Mail. If you want INBOX or UNREAD labels applied, specify them in the message.labelIds field.
Increased the default per-user quotas from 25 units/user/second to 250 units/user/second and adjusted some method costs slightly.
]]>You can now specify the return format for the threads.get method. The available formats are full, metadata, and minimal, similar to the messages.get method. The raw format isn't allowed for the threads.get to avoid unexpectedly large amounts of data being returned.
The getProfile method provides mailbox-wide information like current history ID and total message and thread counts.
Added new fields to the Labels resource to simplify counting how many messages have a given label applied:
messagesTotalmessagesUnreadthreadsTotalthreadsUnreadAdded a new IMPORTANT label to match functionality with the Gmail UI.
The messages.insert method defaults to using receivedTime and the messages.import method defaults to using dateHeader.
When you use the messages.get method, you can request the metadata return format to return only the email headers and metadata such as identifiers and labels.
You can specify the internalDateSource for both the messages.insert and messages.import methods.
Quota costs for all methods in the API have been reduced by a factor of 10. For example, if a method previously cost 150 quota units, it now costs 15. For a complete list of API method costs, see the per-method quota usage chart.
]]>The Gmail API is publicly available!
]]>