MCP Server

Connect Sendivent's MCP server to AI tools for managing events, templates, contacts, notifications, and integrations.

MCP Server URL:

https://mcp.sendivent.com/

Prerequisites

Before connecting, make sure you have:

1. A Sendivent account
2. At least one event configured in your dashboard
3. At least one channel integration set up (email, SMS, Slack, etc.)

Connecting to Sendivent MCP

Choose your AI client to get started:

• Claude — Claude Desktop and Claude Code
• Cursor — Settings UI or config file setup
• GitHub Copilot — VS Code with GitHub Copilot
• Windsurf — Windsurf MCP configuration
• Codex CLI — OpenAI Codex command line
• ChatGPT — ChatGPT connector setup
• Antigravity — Google Antigravity setup
• Raycast — Raycast MCP extension

Looking to add Sendivent to an app built with Lovable, Bolt, v0, or Replit? See AI App Builders.

Authentication

Sendivent uses OAuth 2.0 to securely connect your AI tools. No manual API key management needed.

When you connect for the first time, your client opens a browser window where you sign in to Sendivent. Tokens are stored and refreshed automatically.

Available Tools

Events

Tool	Description
list_events	List all notification events with their channel configuration
get_event	Get event details including templates and routing

Templates

Tool	Description
get_template	Inspect a Handlebars template with variables and channel versions

Contacts

Tool	Description
list_contacts	List contacts with pagination and filtering
get_contact	Get contact by email, phone, UUID, or external ID

Notifications & Deliveries

Tool	Description
list_notifications	List notification runs with filters (event, contact, status)
get_notification	Get notification details including all messages and sequence progress
list_deliveries	List deliveries with filters (event, channel, status, pagination)
trace_delivery	Full delivery trace timeline from trigger to inbox

Integrations

Tool	Description
list_integrations	List all channel integrations and connection status

Notifications

Tool	Description
send_test	Send a test notification in sandbox

Guided Workflows

Send a Test Notification

Your agent can walk through the full send flow:

1. List available events to find the right one
2. Inspect the event's template and required variables
3. Send a test notification to your email in sandbox
4. Trace the delivery to confirm it arrived

Investigate a Failed Delivery

1. List recent deliveries filtered by failed status
2. Use get_notification to see the full notification run including all message attempts
3. Trace the delivery to see the full timeline
4. Check the integration status for the channel
5. Identify the root cause (bounce, invalid address, provider error)

Example Conversations

Event Management

"Show me the event configuration for order.confirmed"
"Which channels are active for the user.welcome event?"
"What templates are assigned to the payment.failed event?"

Notifications & Delivery Tracing

"Show me the notification status for run ID abc-123"
"Show me the last 10 failed deliveries and why they failed"
"Trace the full delivery path for this notification"
"Why did this SMS notification fail and was it retried?"

Templates

"What Handlebars variables are available in the user.welcome template?"
"Show me the email template for order.confirmed"

Contacts & Integrations

"List all my active integrations and their connection status"
"Look up the contact record for user@example.com"

Important Notes

WARNING

Sandbox by default. Test sends go through the sandbox environment to protect production data.

TIP

Handlebars syntax. Templates use double-curly-brace syntax. Payload variables are accessed via payload.variableName.

TIP

Contact resolution. You can reference contacts by email, phone number, UUID, or external ID. Sendivent resolves them automatically.

Next Steps

• Quickstart — Send your first notification via API
• Events — How events and channels work
• Templates — Template variables and rendering
• API Reference — Full endpoint documentation