@sendivent/mcp
v0.2.1
Published
MCP server for Sendivent - Agent-native notification infrastructure
Downloads
192
Maintainers
Readme
@sendivent/mcp
MCP server for Sendivent — multi-channel notification infrastructure for modern apps.
Connect your AI coding agent to your Sendivent account to inspect events, deliveries, contacts, and integrations.
Setup
Remote server (recommended)
claude mcp add --transport http sendivent https://mcp.sendivent.comAuthenticates via OAuth — a browser window opens for Google/GitHub login.
Local server
claude mcp add --transport stdio --env SENDIVENT_API_KEY=your_key sendivent -- npx -y @sendivent/mcpRequires a Sendivent API key (test_ for sandbox, live_ for production).
Tools
| Tool | Description |
|------|-------------|
| list_events | List notification events and enabled channels |
| get_event | Event detail with channel config summaries |
| get_contact | Look up contact by email, phone, UUID, or external ID |
| list_recent_deliveries | Recent deliveries with pagination and filters |
| get_delivery_trace | Full delivery trace timeline for debugging |
| list_integrations | Channel integrations (email domains, Slack workspaces, etc.) |
| send_test | Send test notification (local server with sandbox key only) |
Example prompts
- "What notification events do I have configured in Sendivent?"
- "Show me recent failed deliveries"
- "Look up the contact for [email protected]"
- "What channels are set up in my Sendivent account?"
- "Debug delivery abc-123 — show me the trace"
Safety
- Remote server: Read-only.
send_testis blocked. - Local server (production key): Read-only.
send_testis blocked forlive_keys. - Local server (sandbox key): Full access including test sends.
- Integration secrets (tokens, DKIM keys) are always stripped from responses.
License
MIT
