
Connects Claude to your Gmail account through Pipeworx's gateway, exposing five core operations: listing messages with label and read status filters, fetching full email details including attachments and headers, searching using Gmail's native query syntax (date ranges, senders, attachment presence), sending emails with CC/BCC/attachments, and retrieving all labels. Works via streamable HTTP instead of requiring local setup. You can call tools directly or use the ask_pipeworx interface to query in plain English and let the gateway route to the right Gmail operation. Part of a larger gateway offering 673+ data source integrations under one endpoint.
Gmail MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
gmail_list_messages | List messages in your inbox with optional filtering by label or read status. Returns message IDs, thread IDs, and preview text. Use gmail_search for complex queries like date ranges or attachments. |
gmail_get_message | Fetch full email details by message ID. Returns headers, subject, body text, sender, recipients, attachments, and applied labels. |
gmail_search | Search emails using Gmail query syntax (e.g., 'from:sender@example.com', 'subject:invoice', 'has:attachment', 'after:2024/01/01', 'is:unread'). Returns matching message IDs. |
gmail_send | Send an email with recipient, subject, and body text. Optionally add CC, BCC, reply-to address, and file attachments. |
gmail_list_labels | Get all your labels including system folders (INBOX, SENT, TRASH, DRAFTS) and custom labels. Returns label names and IDs for filtering or organizing. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"gmail": {
"url": "https://gateway.pipeworx.io/gmail/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/gmail/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Gmail data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
This pack runs against a connected gmail account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect gmail, then call POST https://gateway.pipeworx.io/v1/tools/gmail_list_messages with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gmail_list_messages. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.