Trigv MCP server for AI agent alerts
Let Cursor, Claude Code, VS Code, and other MCP clients send Trigv push notifications from agent workflows.
The official MCP server exposes a send_event tool backed by the same Trigv event API.
Best uses
Agent completion alerts
Notify yourself when a long-running coding agent finishes a task, test run, or investigation.
Human approval
Send a push when an agent needs review, credentials, a deploy decision, or manual context.
Workflow failures
Route failed commands, broken builds, and blocked automation steps to a Trigv channel.
Install the MCP server
npm install @trigv/mcpYou can also run it directly from an MCP client with npx -y @trigv/mcp.
Configure your MCP client
Create a Trigv workspace API key, then pass it to the MCP server as TRIGV_API_KEY.
Code
{
"mcpServers": {
"trigv": {
"command": "npx",
"args": ["-y", "@trigv/mcp"],
"env": {
"TRIGV_API_KEY": "trgv_your_api_key_here"
}
}
}
}Tool: send_event
| Field | Use it for |
|---|---|
channel | Route agent alerts to general, deploys, ai, or another Trigv channel. |
title | Short notification headline shown on the device. |
description | Optional context from the agent, command, workflow, or failure. |
level | Use success, warning, or error for quick scanning. |
event_type | Stable event name such as agent.task.completed. |
idempotency_key | Deduplicate retries from the same agent task. |
Example event
Code
{
"channel": "ai",
"title": "Agent task complete",
"description": "Tests passed and the branch is ready for review.",
"level": "success",
"event_type": "agent.task.completed",
"idempotency_key": "agent-task-42"
}Troubleshooting
| Issue | Fix |
|---|---|
| Missing API key | Set TRIGV_API_KEY in the MCP client config. |
| Tool call succeeds but no push arrives | Confirm your device is subscribed to the selected Trigv channel. |
| Channel not found | Use an existing channel slug or create the channel in Trigv first. |