coss-mcp
OfficialRelated Servers
Alternatives to coss-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceOfficial MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.100482 npm1MIT

Sendmux Email Inbox API +official
AlicenseBqualityAmaintenanceSendmux 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.10456MIT- AlicenseNot gradedqualityBmaintenanceEnables authenticated management of email, drafts, sending, domains, contacts, templates, campaigns, workflows, and webhooks through typed MCP tools backed by a REST API.MIT
- AlicenseAqualityCmaintenanceOfficial Notify MCP: send transactional email, rehearse sends, verify sending domains (SPF/DKIM), webhooks and logs from Cursor or Claude Code.21452 npmMIT
- AlicenseBqualityBmaintenanceOfficial 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.55119 npm2MIT
- AlicenseAqualityDmaintenanceMCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.16MIT
TDQS
Scored across 2 tools
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.
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.
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.
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.