How do AI agents use Gmail Postmaster Tools through Open Connector?

Your user connects Gmail Postmaster Tools once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Gmail Postmaster Tools tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Gmail Postmaster Tools MCP server?

Yes. Open Connector can serve Gmail Postmaster Tools as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Gmail Postmaster Tools actions with credentials injected server-side.

Where do Gmail Postmaster Tools credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Gmail Postmaster Tools integration

Gmail Postmaster Tools integration for AI agents.

Gmail Postmaster Tools integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Gmail Postmaster Tools tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Gmail Postmaster Tools actions, managed and audited.

Your user connects Gmail Postmaster Tools once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Gmail Postmaster Tools access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Gmail Postmaster Tools tools.

10 tools are generated from the published Gmail Postmaster Tools catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 10 tools. All published catalog entries are included in this page's server-rendered HTML.

Gmailpostmastertools DomainStats BatchQuery: Executes a batch of QueryDomainStats requests for multiple domains. Returns PERMISSION_DENIED if you don't have permission to access DomainStats for any of the requested domains.; domainstats
Gmailpostmastertools Domains Create: [Developer Preview](https://developers.google.com/workspace/preview): Adds a domain to the user's account. Returns INVALID_ARGUMENT if a domain is not provided. Returns ALREADY_EXISTS if the domain is already registered by the user.; domains
Gmailpostmastertools Domains DomainStats Query: Retrieves a list of domain statistics for a given domain and time period. Returns statistics only for dates where data is available. Returns PERMISSION_DENIED if you don't have permission to access DomainStats for the domain.; domains
Gmailpostmastertools Domains List: Retrieves a list of all domains registered by you, along with their corresponding metadata. The order of domains in the response is unspecified and non-deterministic. Newly registered domains will not necessarily be added to the end of this list.; domains
Gmailpostmastertools Domains Users Create: [Developer Preview](https://developers.google.com/workspace/preview): Creates a user, who has access to a domain. Returns INVALID_ARGUMENT if a user is not provided.; domains
Gmailpostmastertools Domains Users Delete: [Developer Preview](https://developers.google.com/workspace/preview): Deletes a user from a domain. Returns NOT_FOUND if the user does not exist.; domains
Gmailpostmastertools Domains Users Get: [Developer Preview](https://developers.google.com/workspace/preview): Retrieves detailed information about a user that has access to a domain. Returns NOT_FOUND if the user does not exist.; domains
Gmailpostmastertools Domains Users List: [Developer Preview](https://developers.google.com/workspace/preview): Lists the users that have access to a domain.; domains
Gmailpostmastertools Domains Users Patch: [Developer Preview](https://developers.google.com/workspace/preview): Updates a user for a domain. Only Owners and Admins can execute this RPC, only a user's domain permission will be allowed to be updated. Returns NOT_FOUND if the user does not exist. Returns INVALID_ARGUMENT if a permission is not provided or is PERMISSION_UNSPECIFIED, NONE, or OWNER.; domains
Gmailpostmastertools Domains Verify: [Developer Preview](https://developers.google.com/workspace/preview): Verifies a user's ownership of a domain at the DNS level. Note that this is distinct from checking if the user has OWNER status within IRDB.; domains

FAQ

Gmail Postmaster Tools integration, answered

How do AI agents use Gmail Postmaster Tools through Open Connector?: Your user connects Gmail Postmaster Tools once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Gmail Postmaster Tools tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Gmail Postmaster Tools MCP server?: Yes. Open Connector can serve Gmail Postmaster Tools as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Gmail Postmaster Tools actions with credentials injected server-side.
Where do Gmail Postmaster Tools credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Gmail Postmaster Tools — keep the keys.

Open source, self-hostable, with Gmail Postmaster Tools credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →