Skip to main content
Glama
arbengine

mailbox-mcp

Related Servers

Alternatives to mailbox-mcp

  • F
    license
    A
    quality
    D
    maintenance
    An MCP server for semantic search and retrieval of indexed Slack messages stored in Qdrant using Cohere reranking via AWS Bedrock. It enables users to search through Slack history, retrieve full message threads, and access channel or user statistics through natural language.
    5
    -

Related Servers

  • A
    license
    Not graded
    quality
    F
    maintenance
    MCP server that lets AI agents create reviewable physical mail drafts, validate quotes, and pay for postage via MPP or x402 protocols.
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    An open-source MCP server for sending physical mail (letters, postcards, certified mail) directly from AI agents, with per-piece payment and no account signup needed.
    MIT
  • A
    license
    B
    quality
    A
    maintenance
    Official MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.
    100
    513 npm
    1
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.
    16
    MIT

TDQS

A3.5/5.0

Scored across 45 tools

Disambiguation2/5

The set includes many deprecated aliases (e.g. list_agent_inbox vs search_inbound_items, get_agent_inbox_sources vs get_inbound_item) plus overlapping inbound readers and two webhook update tools, so agents must carefully read deprecation notes to choose correctly. Distinct resources exist, but the duplicated old/new paths create real misselection risk.

Naming Consistency4/5

Nearly all names use snake_case verb_noun (list_*, get_*, create_*, update_*), which is predictable. Minor deviations like update_webhook versus update_webhook_endpoint and get_mailbox versus get_mailbox_md keep it from being perfect.

Tool Count2/5

45 tools is far above the ideal range, and much of the excess comes from eleven deprecated aliases that remain served. The useful surface is broad but inflated, making this feel heavy and maintenance-prone.

Completeness4/5

Core lifecycle coverage is good: inbound search/read/pages/actions/quotes, outbound send/list/get/cancel/test/advance, webhook create/list/update/test/deliveries/replay, facility messaging, usage, and MAILBOX.md reads/proposals. Gaps include no delete_webhook_endpoint and no outbound update, but agents can mostly work around them.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive