Checks whether an agent's actions actually happened, against the destination's own records.
Connect Runs on your machine
claude mcp add brydge -e BRYDGE_API_KEY=<BRYDGE_API_KEY> -e BRYDGE_ACTOR=<BRYDGE_ACTOR> -e BRYDGE_URL=<BRYDGE_URL> -- npx -y [email protected]
{
"mcpServers": {
"brydge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>",
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_URL": "<BRYDGE_URL>"
}
}
}
}
{
"mcpServers": {
"brydge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>",
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_URL": "<BRYDGE_URL>"
}
}
}
}
{
"servers": {
"brydge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRYDGE_API_KEY": "<BRYDGE_API_KEY>",
"BRYDGE_ACTOR": "<BRYDGE_ACTOR>",
"BRYDGE_URL": "<BRYDGE_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 |
|---|---|
BRYDGE_API_KEYRequired, secret | Your BRYDGE API key. It starts with brydge_sk_; issue one in BRYDGE on the Connect page. |
BRYDGE_ACTORRequired | The name BRYDGE knows this agent by, such as agent:refund-ops. Mandates are issued to this name. |
BRYDGE_URLOptional | Where BRYDGE runs. Leave it unset for BRYDGE's hosted service. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 2 Oct 2026 |
| Last updated | 2 Oct 2026 |
| Registry name | com.brydge-ai/brydge |
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.
