Skip to main content
Glama
coss-mcp

coss-mcp

Official
by cosscom

coss-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-mcp

Any 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

COSS_MCP_TOOLSETS

Fewer tools: a comma-separated list of email, marketing, inboxes, sms, verify, sign, forms, scheduling, webhooks, hooks, risk, subaccounts, log_drains. Docs, get_setup, logs, get_account_status and api_get are always there. Default: every tool.

COSS_API_KEY

A coss_test_… (development) or coss_live_… (production) key; the server sees that key's environment. Without one, a coss_test_ key in the project's .env.local or .env is used (npx coss-cli init writes it). A coss_live_ key in that file is never loaded. With no key at all, only the docs tools are available.

COSS_BASE_URL

Another API origin, e.g. http://localhost:3001. Defaults to https://api.coss.com.

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_document doesn't exist (upload the PDF with the API or an SDK, then use its id).

  • create_webhook_endpoint returns the signing secret instead of writing it to a file.

  • COSS_MCP_TOOLSETS and COSS_BASE_URL don'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)

search_docs, read_docs

Email delivery

diagnose_email, find_emails, get_email

Sending

send_email, cancel_email, reschedule_email

Suppressions

check_suppression, list_suppressions, add_suppression, remove_suppression

Domains

list_domains, get_domain, add_domain, verify_domain

Webhooks

list_webhook_endpoints, list_webhook_deliveries, get_webhook_delivery, retry_webhook_delivery, create_webhook_endpoint

Receiving

get_inbound_address, list_received_emails, get_received_email

Inboxes

create_inbox, list_inboxes, list_inbox_threads, get_inbox_thread, send_inbox_message, reply_to_inbox_message

SMS

diagnose_sms, find_sms, get_sms, send_sms, cancel_sms, list_received_sms, list_sms_numbers

SMS suppressions

check_sms_suppression, add_sms_suppression, remove_sms_suppression

Logs

search_logs, get_log

Setup

get_setup (with product: that product's readiness and next step)

Templates

list_email_templates, pull_email_template, push_email_template, publish_email_template

Marketing

list_contacts, upsert_contact, list_audiences, save_audience, list_segments, save_segment, list_topics, save_topic, list_broadcasts, get_broadcast, save_broadcast, send_test_broadcast, send_broadcast, cancel_broadcast, get_marketing_settings, update_marketing_settings

Verify

diagnose_verification, start_verification, check_verification, list_verifications, get_verification, cancel_verification, get_verify_settings, update_verify_settings

Sign

diagnose_sign_request, upload_sign_document, list_sign_requests, get_sign_request, get_sign_audit_trail, create_sign_request, create_sign_request_from_template, send_sign_request, remind_sign_request, cancel_sign_request, create_sign_session, list_sign_templates, create_sign_template, get_sign_settings, update_sign_settings

Hooks

diagnose_hook_delivery, list_hook_applications, create_hook_application, list_hook_event_types, create_hook_event_type, list_hook_endpoints, create_hook_endpoint, send_hook_message, send_hook_test_message, list_hook_deliveries, list_hook_attempts, retry_hook_delivery, create_hook_portal_session

Risk

assess_risk, list_risk_assessments, get_risk_assessment, record_risk_feedback, list_risk_rules, list_risk_list_entries, add_risk_list_entry, remove_risk_list_entry, get_risk_settings, check_email_risk, check_ip_risk, check_phone_risk

Forms

diagnose_form_submission, list_forms, get_form, save_form, list_form_submissions, get_form_submission, release_form_submission

Scheduling

diagnose_scheduling_slots, explain_scheduling_slot, list_scheduling_booking_events, get_scheduling_reminders, save_scheduling_reminders, list_scheduling_booking_notifications, mark_scheduling_no_show, list_scheduling_hosts, save_scheduling_host, list_scheduling_schedules, save_scheduling_schedule, list_scheduling_calendars, authorize_scheduling_calendar, list_scheduling_event_types, save_scheduling_event_type, list_scheduling_slots, search_scheduling_availability, list_scheduling_bookings, get_scheduling_booking, create_scheduling_booking, reschedule_scheduling_booking, cancel_scheduling_booking, create_scheduling_session

Sub-accounts

list_subaccounts, get_subaccount, create_subaccount, update_subaccount, delete_subaccount, reinstate_subaccount, get_subaccount_stats

Log drains

list_log_drains, get_log_drain, create_log_drain, update_log_drain, delete_log_drain, list_log_drain_batches

Account

get_account_status

Everything else

api_get: GETs any /v1/ path; refuses anything else, signing secrets and files

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.js

License

MIT

Available Tools

2 tools
read_docsRead a coss.com docs pageA
Read-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 docsA
Read-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

    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

    Related MCP Connectors

    Related MCP Servers

    • 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
    • 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
      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
      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