07 · bridge · 02 systems
Bridges, brokers & protocolsConnective tissue: tool protocols and transports.
Bridges attach agents to tools, data, and channels — tool protocols (MCP), memory servers, and transport bindings that expose an agent through chat or voice. For agents talking to agents, see agent communication.
Systems in this category
Model Context Protocol
Community / OSS · bridge
Model Context Protocol is an open protocol for connecting agents and IDEs to tools and data sources through MCP servers.
instinct-mcp · coding memory
Community / OSS · bridge
instinct-mcp is listed in the official MCP registry as a memory server for coding agents, with pattern detection and confidence scoring. This record covers the coding-memory package, a separate project from the Instinct personal assistant at instinct.com.
Who it's for
Teams extending agents with internal tools, or exposing an agent through Slack, Telegram, or voice.
Tradeoffs
Protocols are stable-ish; brokers and transports are early. None of these write code themselves — they make the agents that do more connected.
Frequently asked
What is a bridge protocol?
Bridges attach agents to tools, data, and channels — tool protocols (MCP), memory servers, and transport bindings that expose an agent through chat or voice. For agents talking to agents, see agent communication.
Who should use a bridge protocol?
Teams extending agents with internal tools, or exposing an agent through Slack, Telegram, or voice.
What are the tradeoffs of bridge protocols?
Protocols are stable-ish; brokers and transports are early. None of these write code themselves — they make the agents that do more connected.
Which bridge protocols are in the catalog?
2 as of 2026-10-20: Model Context Protocol (Community / OSS), instinct-mcp · coding memory (Community / OSS).
What is the Model Context Protocol (MCP)?
An open protocol for connecting agents and IDEs to tools and data sources through MCP servers. It is supported across Cursor, Claude Code, Cline, and many other entries in this catalog.
How are bridges different from agent communication?
Bridges are agent↔tool or agent↔channel — giving one agent new capabilities or a new surface. Agent communication is agent↔agent — discovery, messaging, and delegation between autonomous systems (A2A, Scout, multi-agent frameworks).