BRYDGE
Checks whether an agent's actions actually happened, against the destination's own records.
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Local command
npx -y [email protected]
Credentials from the publisher
- BRYDGE_API_KEY — Your BRYDGE API key. It starts with brydge_sk_; issue one in BRYDGE on the Connect page.
- BRYDGE_ACTOR — The name BRYDGE knows this agent by, such as agent:refund-ops. Mandates are issued to this name.
- BRYDGE_URL — Where BRYDGE runs. Leave it unset for BRYDGE's hosted service.
Provider
Claude Code
BRYDGE_API_KEY=<secret> BRYDGE_ACTOR=<value> BRYDGE_URL=<value> claude mcp add com.brydge-ai-brydge -- npx -y [email protected]
Run in a terminal.
Claude Desktop
{
"mcpServers": {
"com.brydge-ai-brydge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRYDGE_API_KEY": "<secret>",
"BRYDGE_ACTOR": "<value>",
"BRYDGE_URL": "<value>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchRelated MCP
View more- Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
- NNotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
- Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Related skills
View all- reaReverse engineer anything with agents, from app behavior down to native binaries.
- rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
- rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
Checks whether an agent's actions actually happened, against the destination's own records.
README is not crawled yet. Open the repository
- How do I install BRYDGE?
- Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
- Does BRYDGE need an API key?
- The publisher lists these environment variables: BRYDGE_API_KEY, BRYDGE_ACTOR, BRYDGE_URL.
- What transport does BRYDGE use?
- BRYDGE runs locally over stdio.
- When was BRYDGE last checked?
- Last checked 2026-10-16. Checks whether an agent's actions actually happened, against the destination's own records.
No tool list yet. Remote servers get one after the first health check.