No SDKs to install, no agents to run, no YAML to write. Choose MCP for full AI agent integration or drop in a webhook URL for instant event shipping.
Register your app in the dashboard and get a unique API key + webhook URL.
Use MCP for AI agent monitoring or a webhook URL for application events.
Configure channels (email, Slack, Discord) and set your alert rules. Done.
The native protocol for AI agent communication. Add VibeAlerts as an MCP server and every agent action in your workspace automatically reports to your dashboard.
Model Context Protocol (MCP) is an open standard that lets AI coding tools like Cursor, Claude Desktop, and Windsurf communicate with external services. VibeAlerts implements the Streamable HTTP variant — just add a URL and token, no local server needed.
In Cursor, open Settings → MCP or press Cmd+Shift+P and search "MCP".
Click "Add Server" and paste the config below, replacing va_YOUR_TOKEN with your MCP token from the VibeAlerts dashboard.
Restart Cursor to activate the connection. You'll see VibeAlerts listed under MCP servers with a green status indicator.
{ "mcpServers": { "vibealerts": { "url": "https://api.vibealerts.com/api/mcp", "headers": { "Authorization": "Bearer va_YOUR_TOKEN" } } } }
Send alerts, list your apps, query recent events, and check alert rules — all from within your Cursor AI conversation.
Find claude_desktop_config.json at:
macOS: ~/Library/Application Support/Claude/
Windows: %APPDATA%\Claude\
Add the VibeAlerts entry to your mcpServers block. If the file doesn't exist, create it with the content shown.
Fully quit and reopen Claude Desktop. The VibeAlerts tools will appear in the MCP tools panel.
{ "mcpServers": { "vibealerts": { "url": "https://api.vibealerts.com/api/mcp", "headers": { "Authorization": "Bearer va_YOUR_TOKEN" } } } }
In Windsurf, go to Settings → Cascade → MCP Servers and click "Add Server".
Select "HTTP" as the transport type and enter the URL and Authorization header as shown.
The Cascade AI will confirm "vibealerts connected" in the tool panel. Ask it to list your apps to test.
{ "mcpServers": { "vibealerts": { "url": "https://api.vibealerts.com/api/mcp", "headers": { "Authorization": "Bearer va_YOUR_TOKEN" } } } }
Click the Cline icon in the VS Code sidebar, then click the MCP servers icon in the top-right of the panel.
Click "Add Remote Server" and paste the URL. Add the Authorization header in the "Headers" field.
Ask Cline: "Can you list my VibeAlerts apps?" — it will use the MCP tool to query your account.
{ "vibealerts": { "url": "https://api.vibealerts.com/api/mcp", "headers": { "Authorization": "Bearer va_YOUR_TOKEN" }, "transport": "streamable-http" } }
Bolt.new, Lovable, and other browser-based AI tools don't support native MCP config files. Use the Webhook method instead — you can ask the AI to add the webhook call directly to your generated code.
Copy this prompt and paste it into the AI chat after your app is built. The AI will add VibeAlerts reporting to your code automatically.
Add VibeAlerts monitoring to this app.
Whenever an error occurs, a suspicious
request is detected, or an important
event happens, POST to:
https://api.vibealerts.com/webhook/YOUR_APP_KEY
with JSON body:
{
"title": "brief description",
"message": "detailed context",
"category": "security|performance|cost|usage|error",
"alertType": "specific_alert_type",
"severity": "info|warning|critical"
}POST structured JSON to your app's webhook URL. Works from any backend, any language, any framework. No library needed.
{ // Required "title": "string", // Short event title "message": "string", // Detailed context "category": "string", // security|performance|cost|usage|error // Recommended "alertType": "string", // e.g. "brute_force_login" "severity": "string", // info|warning|critical|emergency // Optional enrichment "metadata": {}, // Any additional context "userId": "string", // Affected user ID "requestId": "string" // Trace/request ID }
Every webhook returns 200 OK in under 50ms. Retry-safe, idempotent, and fire-and-forget safe.
async function sendAlert(event) { await fetch( `https://api.vibealerts.com/webhook/${process.env.VA_APP_KEY}`, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(event) } ); } // Usage — in your error handler try { await processOrder(order); } catch (err) { await sendAlert({ title: 'Order processing failed', message: err.message, category: 'error', alertType: 'unhandled_exception', severity: 'critical', metadata: { orderId: order.id } }); }
import httpx, os def send_alert(title, message, category, alert_type=None, severity='warning', metadata=None): url = f"https://api.vibealerts.com/webhook/{os.environ['VA_APP_KEY']}" httpx.post(url, json={ "title": title, "message": message, "category": category, "alertType": alert_type, "severity": severity, "metadata": metadata or {} }, timeout=2) # Usage — FastAPI exception handler @app.exception_handler(Exception) async def handle_exception(request, exc): send_alert( title=f"Unhandled error: {type(exc).__name__}", message=str(exc), category="error", alert_type="unhandled_exception", severity="critical" )
curl -X POST \ https://api.vibealerts.com/webhook/YOUR_APP_KEY \ -H 'Content-Type: application/json' \ -d '{ "title": "Test alert from cURL", "message": "Manual test from terminal", "category": "usage", "alertType": "custom", "severity": "info" }' # Response: {"ok":true,"alertId":"..."}
Define exactly when to notify, what threshold to trigger on, and where to send it. Rules run server-side — no client changes needed.
Each rule defines a trigger condition for a specific alert type. When a matching event arrives, the rule fires and sends to your configured channels.
Every alert type comes with a sensible default rule. Enable in one click, customize the threshold if needed.
Rich HTML emails with alert details, context, and one-click acknowledge. SMTP via your own provider or ours.
Formatted Slack messages with severity color-coding, app name, and direct dashboard link.
Discord webhook embeds with full alert context. Perfect for dev teams already in Discord.
POST to any URL on alert trigger. Build custom PagerDuty, OpsGenie, or Jira integrations.
When connected via MCP, your AI agent can call these tools directly in conversation.
| Tool Name | Description | Example Usage |
|---|---|---|
| send_alert | Send an alert to your VibeAlerts dashboard | "Alert that the migration failed" |
| list_apps | List all registered apps for your account | "What apps am I monitoring?" |
| get_recent_alerts | Fetch alerts from the last N hours | "Show me critical alerts from today" |
| get_alert_catalog | Browse available alert types by category | "What security alerts can I send?" |
| get_dashboard_stats | Fetch summary stats for an app | "How many alerts this week for my-app?" |
Go to Settings → API Keys in the VibeAlerts dashboard. Click "Generate MCP Token" — this creates a 365-day token scoped to MCP operations. Store it in your config file, never commit it to git.
Create your account, get an API key, and paste the MCP config. 30 seconds.
Create Free Account