Deterministic execution authorization for AI agents and automated systems.
Connect Runs on your machine
claude mcp add trigguard -e TRIGGUARD_API_KEY=<TRIGGUARD_API_KEY> -e TRIGGUARD_ORG_ID=<TRIGGUARD_ORG_ID> -e TRIGGUARD_GATEWAY_URL=<TRIGGUARD_GATEWAY_URL> -- npx -y @trigguard/[email protected]
{
"mcpServers": {
"trigguard": {
"command": "npx",
"args": [
"-y",
"@trigguard/[email protected]"
],
"env": {
"TRIGGUARD_API_KEY": "<TRIGGUARD_API_KEY>",
"TRIGGUARD_ORG_ID": "<TRIGGUARD_ORG_ID>",
"TRIGGUARD_GATEWAY_URL": "<TRIGGUARD_GATEWAY_URL>"
}
}
}
}
{
"mcpServers": {
"trigguard": {
"command": "npx",
"args": [
"-y",
"@trigguard/[email protected]"
],
"env": {
"TRIGGUARD_API_KEY": "<TRIGGUARD_API_KEY>",
"TRIGGUARD_ORG_ID": "<TRIGGUARD_ORG_ID>",
"TRIGGUARD_GATEWAY_URL": "<TRIGGUARD_GATEWAY_URL>"
}
}
}
}
{
"servers": {
"trigguard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@trigguard/[email protected]"
],
"env": {
"TRIGGUARD_API_KEY": "<TRIGGUARD_API_KEY>",
"TRIGGUARD_ORG_ID": "<TRIGGUARD_ORG_ID>",
"TRIGGUARD_GATEWAY_URL": "<TRIGGUARD_GATEWAY_URL>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
TRIGGUARD_API_KEYRequired, secret | TrigGuard gateway API key (tg_live_…) |
TRIGGUARD_ORG_IDRequired | Organisation id sent as X-Consumer on POST /v1/authorize |
TRIGGUARD_GATEWAY_URLOptional | Execution gateway origin (default https://api.trigguardai.com) |
Details
| Package | @trigguard/[email protected] (NPM, stdio) |
| First published | 8 Sep 2026 |
| Last updated | 8 Sep 2026 |
| Registry name | io.github.TrigGuard-AI/trigguard |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
