Drin MCP Server
Enables MCP-capable agents to send, receive, and manage email, including domains, inboxes, contacts, templates, webhooks, and delivery metrics, through the Drin API.
README
@drin00/mcp
A Model Context Protocol server for the complete Drin email loop. Give any MCP-capable agent — Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Devin, your own — the ability to send and receive email, parse inbound messages, keep threads, reply with human approval, and manage domains, inboxes, contacts, templates, webhooks, API keys, integrations, and delivery metrics — full parity with the Drin dashboard, authenticated with a single Drin API key.
Zero third-party dependencies. Runs on Node 20+. Free on every Drin plan.
Install
No install needed — point your MCP client at it with npx:
{
"mcpServers": {
"drin": {
"command": "npx",
"args": ["-y", "@drin00/mcp"],
"env": { "DRIN_API_KEY": "drin_your_key" }
}
}
}
Create an API key in the dashboard under Settings → API Keys. If the key is
account-wide (not scoped to one product), also set DRIN_SENDER to a product
externalId.
Claude Desktop
Add the block above to claude_desktop_config.json
(macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\),
then restart Claude.
Claude Code
claude mcp add drin -e DRIN_API_KEY=drin_your_key -- npx -y @drin00/mcp
Cursor / Windsurf / VS Code
Add the same mcpServers block to the editor's MCP config
(~/.cursor/mcp.json, Windsurf settings, or .vscode/mcp.json).
Configuration
| Env var | Required | Default | Purpose |
|---|---|---|---|
DRIN_API_KEY |
yes | — | Bearer token (Settings → API Keys) |
DRIN_BASE_URL |
no | https://api.drin.run |
Override for self-hosted/preview |
DRIN_SENDER |
no | — | Default product externalId (account-wide keys) |
Flags --api-key, --base-url, --sender override the env vars.
Tools
54 tools spanning the whole Drin API — everything the dashboard does, an agent can do.
| Group | Tools |
|---|---|
| Sending | send_email, send_batch, reply_email |
| Reading | list_emails, get_email, get_email_body, list_email_attachments |
| Domains | list_domains, get_domain, add_domain, verify_domain, delete_domain, get_domain_receiving, set_domain_receiving |
| Inboxes | list_inboxes, create_inbox, get_inbox, delete_inbox |
| Threads | list_threads, get_thread |
| Inbound | simulate_inbound |
| Contacts | list_contacts, create_contact, get_contact, update_contact, unsubscribe_contact, resubscribe_contact, delete_contact |
| Suppressions | list_suppressions, add_suppression, remove_suppression |
| Templates | list_templates, get_template, create_template, update_template, delete_template, render_template, preview_template, list_template_gallery |
| Webhooks | list_webhooks, get_webhook, create_webhook, update_webhook, delete_webhook |
| API keys | list_api_keys, create_api_key, revoke_api_key |
| Metrics | get_metrics |
| Account | list_account_messages (tenant-wide feed across all products) |
| Integrations | list_integrations, get_integration, install_integration, update_integration, uninstall_integration |
Addresses accept "Name <email>" or a bare "email"; recipient fields accept a
string or an array of strings. Show-once secrets (new API keys, webhook signing
secrets) are returned only on the create call — persist them immediately.
Programmatic use
import { createDrinMcpServer } from "@drin00/mcp";
const server = createDrinMcpServer({
apiKey: process.env.DRIN_API_KEY!,
sender: "acme", // optional, for account-wide keys
});
await server.serve(); // wires stdin/stdout
Security
The server speaks only to the Drin API over HTTPS using your Bearer key — there
is no separate auth surface. Everything the key is allowed to do, the agent can
do; scope the key to one product and the minimum it needs. Keys are shown once
on creation; store them in your MCP client's env, never in source.
Develop
npm run typecheck # tsc on src + tests
npm run build # emit dist/
npm test # node:test unit suite
MIT licensed.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。