coss-mcp
Officialcoss-mcp
The Model Context Protocol server for coss.com. Your coding agent can ask "did the welcome email to jane@example.com get delivered?" (or "did the code we texted +14155550123 arrive?") and get the answer: the message, what happened to each recipient and why, and what to do about it.
claude mcp add coss -e COSS_API_KEY=coss_test_… -- npx -y coss-mcpAny MCP client works the same way: run npx -y coss-mcp with COSS_API_KEY in its environment.
Setup for Cursor, VS Code and Codex: coss.com/docs/mcp. A client that
can't start a local process can use the hosted server.
Published from cosscom/coss by CI, with provenance.
Configuration
Variable | |
| Fewer tools: a comma-separated list of |
| A |
| Another API origin, e.g. |
Configuration is read from the environment only, never from command-line arguments, which other local processes can read.
API keys can do everything the API can: through this server the agent can also send email and SMS
and change suppressions and domains. Tools are annotated (readOnlyHint, destructiveHint) so clients
can ask before calling the ones that change something.
Related MCP server: mailbox-mcp
Hosted server
The same tools, prompts and resources at https://api.coss.com/mcp: Streamable HTTP, stateless, with
nothing to install.
Authenticate with Authorization: Bearer <API key>. There's no OAuth sign-in, so the client has to
let you set a custom header.
claude mcp add --transport http coss https://api.coss.com/mcp \
--header "Authorization: Bearer coss_test_…"Cursor, VS Code, Codex and others: coss.com/docs/mcp. Use a
development key (coss_test_…) unless you need production data.
Each tool calls the public API with your key, so its permissions, rate limits and logs apply as usual. What's different from the local server:
It can't touch your files: it doesn't read a project's env file, and
upload_sign_documentdoesn't exist (upload the PDF with the API or an SDK, then use its id).create_webhook_endpointreturns the signing secret instead of writing it to a file.COSS_MCP_TOOLSETSandCOSS_BASE_URLdon't apply. Requests take at most 50 seconds and 1 MB, an API call's answer at most 8 MB of JSON, and browsers' requests are refused.
server.json describes both for the MCP registry.
Tools
Area | Tools |
Docs (no key needed) |
|
Email delivery |
|
Sending |
|
Suppressions |
|
Domains |
|
Webhooks |
|
Receiving |
|
Inboxes |
|
SMS |
|
SMS suppressions |
|
Logs |
|
Setup |
|
Templates |
|
Marketing |
|
Verify |
|
Sign |
|
Hooks |
|
Risk |
|
Forms |
|
Scheduling |
|
Sub-accounts |
|
Log drains |
|
Account |
|
Everything else |
|
Prompts: add_product, debug_delivery, prepare_go_live. Resources: coss://docs/index (no key
needed), coss://setup. get_setup and the diagnose_* tools declare an outputSchema.
As a library
createCossMcpServer returns the server unconnected, for another transport or an existing client:
import { Coss } from "coss";
import { createCossMcpServer } from "coss-mcp";
const apiKey = process.env.COSS_API_KEY;
const server = createCossMcpServer({ coss: new Coss({ apiKey }), apiKey });diagnoseEmail({ email, events, context }) and diagnoseSms({ sms, events, context }), the pure
functions behind diagnose_email and diagnose_sms, come from the SDK's coss/diagnose (re-exported
here), as do the other products' diagnoses.
Development
bun run --cwd packages/mcp build # tsdown, publint, attw
bun run --cwd packages/mcp test
COSS_API_KEY=coss_test_… COSS_BASE_URL=http://localhost:3001 npx @modelcontextprotocol/inspector node packages/mcp/dist/cli.jsLicense
MIT
Available Tools
2 toolsread_docsRead a coss.com docs pageARead-only
One page of coss.com's documentation as Markdown: a guide, an SDK page, or an API reference page (method and URL, parameters, request body, responses, errors and examples in each SDK). Takes a path from search_docs or a docs link, e.g. "/docs/email/sending" or "/docs/api-reference/emails/send-email"; "/docs" is the index of every section. Works without an API key.
Inputs: page (required), offset.
search_docsSearch the coss.com docsARead-only
Searches coss.com's documentation (guides, SDK pages and the API reference) and returns the matching pages with the passages that matched. Read a page in full with read_docs. Works without an API key.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
Official remote MCP server of MailSenpai, the EU-hosted email marketing platform. Connect Claude, ChatGPT, Cursor or another MCP client with OAuth 2.1 and PKCE. 74 tools manage lists, subscribers, segments, templates, draft campaigns and stats, and check email DNS, blacklists and spam. Sends and deletions require explicit confirmation; every call is logged. The same team also offers SMTP Senpai, an SMTP relay and email API for transactional sending: https://en.mailsenpai.com/smtp-senpai/.
Official MCP server for twitterapis.com. Twitter/X search, users, DMs, Grok, monitoring and writes.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.16MIT
- 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

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- AlicenseBqualityBmaintenanceOfficial MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.100482 npm1MIT