@trigv/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRIGV_API_KEY | Yes | Workspace ingest API key (trgv_…) | |
| TRIGV_BASE_URL | No | Override for local dev | https://api.trigv.com/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_eventA | Send a notification event to a Trigv workspace channel. Requires TRIGV_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only 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.