Skip to main content
Glama
baryhuang

MCP Headless Gmail Server

by baryhuang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Headless Gmail Server

No user-submitted related servers found.

    Related Servers

    • MCP Headless Gmail Server

      AbhinavBansal17
      A
      license
      B
      quality
      D
      maintenance
      Enables reading and sending Gmail messages in headless/remote environments without local credential storage, using OAuth tokens passed directly in API calls for containerized deployments.
      3
      14 npm
      MIT

    • QCH-Hermes

      seenark
      F
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted Gmail gateway MCP server that enables searching and fetching emails from multiple authorized Gmail mailboxes via a single backend authorization boundary.
      -

    • Gmail MCP Server

      Ansh-Wappnet
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables applications to interact with Gmail through a clean API, supporting email searching, sending, reading, and label management.
      MIT

    • honest-gmail-mcp

      bartosz-kuc
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that provides Gmail tools (search, read, send, draft, label management) while keeping your emails only between your machine and Google, with no third-party access.
      6
      MIT

    • gmail-mcp-server

      ivanlhz
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that exposes the Gmail API for integration with LLMs, enabling email management tasks such as reading, labeling, and searching emails.
      7
      MIT
    Deploy Server
    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

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: retrieving email body chunks, listing recent emails, refreshing tokens, and sending emails. There is no overlap in functionality that would cause confusion or misselection.

    Naming Consistency5/5

    All tools follow a consistent 'gmail_verb_noun' pattern with snake_case, making them predictable and easy to understand. The naming convention is uniform across all four tools.

    Tool Count4/5

    With 4 tools, the count is reasonable for a Gmail server, though it feels slightly thin for covering all common email operations. It includes core functions but could benefit from additional tools like searching or managing drafts.

    Completeness3/5

    The tools cover basic email operations (read, list, send) and authentication, but there are notable gaps such as searching emails, managing labels, or handling attachments. This could limit agents in performing more complex email tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources