Skip to main content
Glama
tarunlnmiit

inbox-to-action-mcp

by tarunlnmiit

Related Servers

Alternatives to inbox-to-action-mcp

  • A
    license
    B
    quality
    F
    maintenance
    MCP server that connects Claude with Gmail to read, send, delete, and manage messages and labels via the Google Gmail API.
    3
    MIT

Related Servers

  • F
    license
    A
    quality
    C
    maintenance
    A secure Gmail MCP server that lets Claude search, read, and triage mail, draft replies, and send drafts—with encrypted credential storage, scoped OAuth permissions, and explicit human checkpoints before any irreversible action.
    6
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    A local MCP server that gives Claude access to multiple Gmail accounts simultaneously for search, read, draft, send, label, and a scheduled cross-inbox digest, with enforced send policies per mailbox.
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI-powered Gmail triage: fetches unread emails, classifies them, drafts replies for important ones, and sends only after user approval via conversational review. Exposes tools for checking unread emails and submitting review feedback from Claude Desktop or any MCP client.
    -
  • A
    license
    A
    quality
    D
    maintenance
    A privacy-first MCP server for inbox triage, enabling masked email reading, calendar upsert, reply drafting, and Slack digests using Google and Slack credentials.
    10
    MIT
  • F
    license
    A
    quality
    D
    maintenance
    Local stdio MCP server enabling Claude to send Gmail, search emails with attachment metadata, and download attachments to Google Drive.
    2
    3
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for human-reviewed Zoho Mail inbox triage. It uses a two-pass proposal/execution model to propose actions (move, archive, mark-read) without touching the inbox until a human approves, and treats email content as untrusted data to prevent prompt injection.
    -

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: fetching emails, appending tasks, saving drafts, and writing reports. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (append_tasks, fetch_emails, save_gmail_draft, write_report), making it easy to predict their function.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of email triage and task extraction. Each tool serves a necessary function without being excessive or insufficient.

Completeness4/5

The tool set covers the core workflow of fetching, drafting, and recording tasks/reports. Minor gaps exist (e.g., no tool to mark emails as read or delete tasks), but these are acceptable for a demo/triage system.

Maintenance

ActivityStale
ResponsivenessNo issues