Skip to main content
Glama
coss-mcp

coss-mcp

Official
by cosscom

Related Servers

Alternatives to coss-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Official MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.
      100
      482 npm
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Sendmux is an email inbox API and email API for AI agents. Use this MCP server to let authorised agents work with Sendmux mailboxes, inbound email, clean JSON parsing, webhooks, outbound sending, provider routing, logs, billing, and team controls.
      104
      56
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables authenticated management of email, drafts, sending, domains, contacts, templates, campaigns, workflows, and webhooks through typed MCP tools backed by a REST API.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Official Notify MCP: send transactional email, rehearse sends, verify sending domains (SPF/DKIM), webhooks and logs from Cursor or Claude Code.
      21
      452 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Official mailbox.bot MCP server for AI agents. Send letters, certified mail and postcards, and give an agent its own street address + postal mailbox number. Agent receiving virtual mailboxes with a real street address are live now at $15/mo in Manhattan Beach, CA. Sandbox keys, approval controls, tracking and webhooks.
      55
      119 npm
      2
      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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    search_docs and read_docs are the classic find-then-fetch pair with clearly separated roles: one returns matching passages, the other returns a full page as Markdown. The read_docs description explicitly states it takes a path from search_docs, reinforcing the intended workflow rather than creating overlap.

    Naming Consistency5/5

    Both tools follow the same verb_noun snake_case pattern (search_docs, read_docs) with a shared resource suffix. There is no mixing of conventions or vague verbs.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but for a read-only documentation server this pair is exactly the minimal viable surface — nothing is redundant. It is thin but not under-scoped.

    Completeness5/5

    Search covers discovery, read_docs covers retrieval of any guide, SDK page, or API reference, and the /docs index path provides a browse entry point. There are no obvious dead ends for the stated purpose of reading coss.com documentation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues