Skip to main content
Glama

README.md not found. View project on GitHub.

Available Tools

10 tools
createInboxD

Create a new inbox

Inputs: display_name, domain, username.

getAttachmentC

Get attachment by ID

Inputs: attachment_id (required), inbox_id (required), message_id (required).

getInboxC

Get inbox by ID

Inputs: inbox_id (required).

getMessageC

Get message by ID

Inputs: inbox_id (required), message_id (required).

getThreadC

Get thread by ID

Inputs: inbox_id (required), thread_id (required).

listInboxesC

List all inboxes

Inputs: limit, offset.

listMessagesD

List messages

Inputs: inbox_id (required), limit, offset.

listThreadsC

List threads by inbox ID

Inputs: inbox_id (required), limit, offset.

replyToMessageD

Reply to a message

Inputs: inbox_id (required), message_id (required), text (required), html, +1 more.

sendMessageD

Send a message

Inputs: inbox_id (required), subject (required), text (required), to (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions. For example, createInbox vs. getInbox vs. listInboxes are distinct operations on inboxes, and getMessage vs. sendMessage vs. replyToMessage handle different message interactions. There is no ambiguity or overlap in functionality.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern throughout, such as createInbox, getInbox, listInboxes, sendMessage, and replyToMessage. However, there is a minor deviation with getAttachment (using 'get' instead of a more specific verb like 'download' or 'retrieve'), but overall the pattern is predictable and readable.

    Tool Count5/5

    With 10 tools, this server is well-scoped for an email/communication domain. Each tool earns its place by covering essential operations like inbox management, message handling, and threading, without being overly sparse or bloated. The count aligns well with typical MCP server ranges.

    Completeness4/5

    The tool surface provides strong coverage for core email workflows, including CRUD operations for inboxes, messages, and threads, as well as actions like sending and replying. A minor gap is the lack of tools for deleting or updating messages/inboxes, but agents can work around this, and the set supports most common use cases effectively.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      Provides an interface to manage email marketing, contact lists, dynamic templates, and email analytics via SendGrid's API.
      21
      32
      -
    • A
      license
      D
      quality
      D
      maintenance
      An MCP-based email tool that enables AI models to access email services through standardized interfaces, allowing AI assistants to perform various email operations like sending emails, reading inboxes, and handling attachments.
      17
      51
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      A server that enables AI assistants to interact with the Omnisend marketing platform, supporting contact management, product management, and event tracking operations through natural language.
      17
      1
      Apache 2.0