Hosted MCP connectors

Your tools, wired to your AI assistant.

MCP Wave builds and hosts Model Context Protocol connectors, so an AI assistant you already use can work directly with your everyday services — securely, on your instruction, with you in control of what it may do.

Advanced Gmail

Our first connector links your Gmail account (or several) to your assistant. Once you connect it, you can ask your assistant to do the things you'd otherwise do by hand:

Search and read mail, and summarize what needs your attention
Write replies as drafts for you to review before anything goes out
Organize: labels, archiving, and moving mail to Trash
Create and manage Gmail filters so recurring mail sorts itself
Send mail — only to recipients you have approved (see below)
Connect more than one mailbox and work across all of them at once

You decide what it may do

The connector is built to be conservative by default, because it is acting on your real mailbox:

Sending is gated

By default your assistant may only send to your own address. Any other recipient must be approved by you — once, or added to an allowlist you control.

Deleting is gated

Moving mail to Trash is ordinary and reversible. Permanent deletion always asks you to confirm first.

You choose the mailboxes

Add or remove connected accounts at any time from the setup screen shown when you connect.

You can revoke anytime

Disconnect in your AI assistant, or remove access directly in your Google Account permissions.

What Google data we access, and why

We request only the Google permissions the features above require. We use this data solely to carry out the actions you ask your assistant to perform.

.../auth/gmail.modify

Read, compose, send, and organize your mail — the core of triage, drafting, labeling, and archiving.

.../auth/gmail.settings.basic

Read and manage Gmail filters and send-as addresses, so recurring mail can be sorted and replies can come from the right address.

openid, email

Identify which Google account you connected, so the right mailbox is used.

We do not sell your data, use it for advertising, or use it to train generative AI models. Full detail — including our Limited Use commitment — is in the Privacy Policy.

How it is protected

Google authorization tokens are encrypted at rest and never shown to anyone
All traffic is over TLS; the service runs on Google Cloud
Each connection is isolated to the account that authorized it
We request the narrowest permissions that make the features work

Contact

Questions, data requests, or security reports: support@mcpwave.com.