Skip to main content
Glama
pipeworx-io

mcp-gmail

by pipeworx-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp-gmail

Gmail MCP Pack

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

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.

Related MCP server: Gmail MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "gmail": {
      "url": "https://gateway.pipeworx.io/gmail/mcp"
    }
  }
}

What this endpoint actually serves

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 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

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":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-gmail"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-gmail

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

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.

More

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • mcp-gmail

    jeremyjordan
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Gmail access through MCP, allowing LLMs to read, compose, and send emails.
    10
    MIT

  • Gmail MCP Server

    cristip73
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Gmail through the MCP protocol, supporting sending, reading, searching, replying, forwarding, managing drafts and labels, and saving attachments.
    5 npm
    3
    MIT

  • Gmail MCP Server

    david-strejc
    A
    license
    A
    quality
    D
    maintenance
    Enables Gmail management via MCP, including email search, retrieval, labeling, sending, and forwarding through IMAP and SMTP.
    15
    11
    BSD 3-Clause

  • Moist

    TickTockBent
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Gmail operations such as reading, sending, searching, and managing emails, threads, labels, and drafts via MCP tools.
    1
    MIT