Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@trigv/mcp Send a deploy completed notification to the deploys channel"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for Trigv. Lets AI clients in Cursor, Claude Code, and VS Code send notification events to your Trigv workspace.
Trigv delivers developer notifications to your team's devices. Your backend (or AI agent) sends lightweight JSON events; Trigv queues push delivery. Notification title and body are not stored on Trigv servers — metadata only.
Related MCP server: SuprSend MCP Server
npm install @trigv/mcpOr run directly with npx:
npx @trigv/mcpCreate a workspace API key at app.trigv.com.
Set TRIGV_API_KEY in your MCP client config (see below).
Ask your AI assistant to send an event using the send_event tool.
Example tool call:
{
"channel": "deploys",
"title": "Production deploy complete",
"description": "Build #42 succeeded in 38s (commit abc1234)",
"level": "success",
"event_type": "deploy.completed",
"idempotency_key": "deploy-prod-42"
}Variable | Required | Default | Description |
| Yes | — | Workspace ingest API key ( |
| No |
| Override for local dev ( |
The API key is sent as Authorization: Bearer and is never included in tool responses or error messages.
send_eventSends a notification event via POST /v1/events.
Field | Required | Description |
| Yes | Channel slug (e.g. |
| Yes | Notification title |
| No | Body text |
| No | HTTPS image URL (not stored server-side) |
| No | Destination URL for the notification (max 2048 characters; not stored server-side) |
| No |
|
| No |
|
| No | Free-form label (e.g. |
| No | Dedup key per workspace |
Success response includes event.public_id, duplicate (true when HTTP 200), and other event metadata.
Error response includes error.type, error.message, and optional error.errors for validation failures.
info — general information (default)
success — completed successfully
warning — attention needed
error — failure or alert
standard — normal notifications (default)
time_sensitive — iOS Time Sensitive delivery
When you set idempotency_key, retries with the same key return the existing event (duplicate: true) without billing again.
Error type | When |
| Missing |
| Invalid input (client or server 422) |
| HTTP 401 |
| HTTP 403 |
| Channel not found (HTTP 404) |
| HTTP 429 |
| Connection issues |
Add to .cursor/mcp.json in your project (or global Cursor MCP settings):
{
"mcpServers": {
"trigv": {
"command": "npx",
"args": ["-y", "@trigv/mcp"],
"env": {
"TRIGV_API_KEY": "trgv_your_api_key_here"
}
}
}
}For a local checkout during development:
{
"mcpServers": {
"trigv": {
"command": "node",
"args": ["/path/to/trigv-mcp/dist/index.js"],
"env": {
"TRIGV_API_KEY": "trgv_your_api_key_here",
"TRIGV_BASE_URL": "http://trigv-platform.test/api"
}
}
}
}Add to ~/.claude/settings.json or project .claude/settings.json:
{
"mcpServers": {
"trigv": {
"command": "npx",
"args": ["-y", "@trigv/mcp"],
"env": {
"TRIGV_API_KEY": "trgv_your_api_key_here"
}
}
}
}Add to .vscode/mcp.json in your workspace:
{
"servers": {
"trigv": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@trigv/mcp"],
"env": {
"TRIGV_API_KEY": "trgv_your_api_key_here"
}
}
}
}{ "channel": "general", "title": "Hello from MCP" }{
"channel": "deploys",
"title": "Production deploy complete",
"description": "Build #42 succeeded in 38s (commit abc1234)",
"level": "success",
"delivery_urgency": "standard",
"event_type": "deploy.completed",
"idempotency_key": "deploy-prod-42"
}{
"channel": "alerts",
"title": "Nightly backup failed",
"description": "Exit code 1 after 12 minutes",
"level": "error",
"event_type": "cron.failed"
}git clone https://github.com/Trigv/trigv-mcp.git
cd trigv-mcp
npm install
npm run build
npm testRun locally:
TRIGV_API_KEY=trgv_… npm run devnpm testTests use mocked HTTP — no live API key required in CI.
See the Trigv SDK programme for API contract and conformance requirements.
MIT — see LICENSE.
Send a notification event to a Trigv workspace channel. Requires TRIGV_API_KEY.
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | Notification level (default: info) | |
| title | Yes | Notification title | |
| channel | Yes | Channel slug (e.g. general, deploys) | |
| image_url | No | Optional HTTPS image URL (not stored server-side) | |
| event_type | No | Free-form event label (e.g. deploy.completed) | |
| description | No | Optional body text (not stored server-side) | |
| idempotency_key | No | Dedup key per workspace; retries return the existing event | |
| delivery_urgency | No | Delivery urgency (default: standard) |
| Name | Required | Description |
|---|---|---|
| error | No | |
| event | No | |
| success | Yes | |
| duplicate | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the auth requirement (TRIGV_API_KEY), which is important. However, it does not mention other behavioral traits such as idempotency (hinted at in schema), side effects, or whether the call is safe or mutating. With no annotations, the description could provide more context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that effectively conveys the core action and a critical requirement. No unnecessary words; it is appropriately concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 8 parameters (some with enums) and an output schema, the description is minimal. It covers the essential purpose but does not provide additional context on when to include optional parameters or typical usage patterns. The presence of an output schema mitigates the need to explain return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond 'Send a notification event to a Trigv workspace channel'—it does not elaborate on any parameters or their roles, so it meets but does not exceed the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Send', the resource 'notification event', and the destination 'Trigv workspace channel'. It explicitly distinguishes the tool's purpose despite no siblings, and the required API key adds context. No ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for sending notifications to a workspace channel and mentions a prerequisite (API key). However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria, though the context of sending events is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0send_eventOnly one tool exists, so there is no ambiguity. The single tool has a clear, distinct purpose.
With only one tool, naming consistency is perfect as there are no other tools to conflict with. The name 'send_event' follows a clear verb_noun pattern.
A single tool is borderline; while it may be sufficient for a very narrow purpose, it feels thin compared to the typical 3-15 tools for a well-scoped server.
The server only provides a send operation, missing other expected capabilities like event listing, deletion, or configuration, which limits its usefulness for agents.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Connect AI tools to Trilo workspaces — manage tasks, messages, pages, calendars, meetings, and more.
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
Create Tasks and run Workflows in Bleep from Claude, ChatGPT, and other AI assistants.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Trigv/trigv-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
