coss-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COSS_API_KEY | No | 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 | No | Another API origin, e.g. http://localhost:3001. Defaults to https://api.coss.com. | https://api.coss.com |
| COSS_MCP_TOOLSETS | No | 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. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for coss.com, the developer platform for email, SMS, one-time codes, e-signatures, forms, scheduling, webhooks (Hooks) and risk checks.
search_docs and read_docs search and read coss.com's documentation as Markdown (guides, SDKs, and the API reference with every operation's parameters, bodies and responses): read the relevant page before writing code against coss.com.
No COSS_API_KEY is configured, and the project's .env.local or .env has no development (coss_test_) key, so only the docs tools are available. To get one, run npx coss-cli init in the project (the user approves it in the browser; it is written to .env.local or .env). Restart this server afterwards: it reads that file when its own environment has no key. A coss_live_ key in the file is never loaded.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | 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. |
| read_docsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs_index | coss.com's guides, and a link to each product's API operations. read_docs reads a page. |
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.