Skip to main content
Glama
WalidMoultamiss

CocoInbox MCP Server

by WalidMoultamiss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to CocoInbox MCP Server

No user-submitted related servers found.

    Related Servers

    • imap-mail-mcp

      julioc-barros
      A
      license
      B
      quality
      A
      maintenance
      Connects MCP clients to any IMAP/SMTP email account, enabling email search, reading, sending, replying, forwarding, flagging, moving, and folder management via natural language.
      17
      MIT

    • simple-email-mcp

      mexican75
      A
      license
      B
      quality
      B
      maintenance
      Enables users to manage email accounts via IMAP/SMTP, including reading, searching, sending emails with attachments and calendar invites, all through natural language interactions with MCP-compatible clients.
      1
      4
      MIT

    • postbus-mcp

      HalloSouf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching, reading full conversations, and sending email across multiple IMAP/SMTP mailboxes from any MCP client, with multi-user support and per-user API tokens.
      MIT

    • mcp-email-server

      fastmcp-me
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and sending emails via IMAP and SMTP through the MCP protocol. Supports multiple email accounts and configuration via UI or environment variables.
      BSD 3-Clause

    • anymail-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.
      3 npm
      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.1/5.0

    Scored across 35 tools

    Disambiguation2/5

    Several tools overlap heavily: login, connect, complete_login, and login_with_password all handle authentication, while request_missing_tool is an alias for submit_idea and list_my_tool_requests is an alias for list_my_ideas. create_folder and create_folder_for_email also have blurred boundaries. The CRM and security clusters are clearer, but overall an agent could easily select the wrong auth or alias tool.

    Naming Consistency4/5

    Most tools consistently use snake_case verb_noun naming, and the crm_* cluster is very coherent. However, bare/alias names like connect, request_missing_tool, and list_my_tool_requests break the pattern, and domain prefixes are inconsistently applied across auth, mail, security, and company tools.

    Tool Count2/5

    With 35 tools, this exceeds the 25+ threshold for 'too many'. The set spans auth, mail, security, ideas, CRM, and company profile, but several tools are aliases or near-duplicates, so the count feels inflated rather than well-scoped. Consolidating auth entry points and removing aliases would bring it closer to a reasonable size.

    Completeness3/5

    Core workflows exist for authentication, ephemeral email, dark-web scanning, ideas, company profile, and CRM lead/task management. However, lifecycle coverage has notable gaps: there is no delete for folders, emails, leads, groups, or tasks, and no general task creation outside generated prospect tasks. These gaps create dead ends that agents can partially work around but not fully resolve.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources