mcp-agent-bridge

mcp-agent-bridge serves as a connectivity bridge that enables smooth communication between multiple AI agent systems, specifically enabling integration between Codex CLI, Claude CLI, Gemini CLI, and Agent Zero. Once running, you can route prompts and responses between these agents through the bridge, allowing you to orchestrate tasks that leverage the strengths of each model. The bridge focuses on providing a unified interface for agent-to-agent coordination, task delegation, and data sharing, so you can build workflows where one agent handles planning while another executes actions or fetches results.

To use the tool, start the container (or run the binary if you obtain a local build), then configure your agent endpoints and authentication details as needed. The bridge exposes a coordination surface that agents can subscribe to or publish to, enabling bidirectional communication and message routing. Use the provided UI or config files to map specific intents to the corresponding agent CLI, ensuring that prompts are directed to the most appropriate model for the task at hand.

Prerequisites:

• Docker installed and running on your system (Linux, macOS, or Windows with WSL).
• Internet access to pull the image from the registry.

Installation steps:

1. Pull the Docker image: docker pull alyamani18/mcp-agent-bridge

2. Run the container interactively to start the bridge: docker run -it --rm
   -v /path/to/config:/app/config
   -e BRIDGE_CONFIG=/app/config/config.yaml
   alyamani18/mcp-agent-bridge

3. If you prefer to run a detached container: docker run -d --name mcp-agent-bridge
   -v /path/to/config:/app/config
   -e BRIDGE_CONFIG=/app/config/config.yaml
   alyamani18/mcp-agent-bridge

4. Verify the service is up by checking logs: docker logs -f mcp-agent-bridge

5. If you have a local configuration file, place it in the mounted config path and reference it via BRIDGE_CONFIG as shown above.

Notes and tips:

• Environment variables: BRIDGE_CONFIG can point to a YAML/JSON configuration file that defines agent endpoints, authentication tokens, and routing rules. If your deployment uses different paths, adjust the volume mount and env variable accordingly.
• Compatibility: The bridge is designed to work with Codex CLI, Claude CLI, Gemini CLI, and Agent Zero; ensure you have the corresponding CLI tools installed and accessible from within the container if the bridge needs to invoke them directly.
• Networking: When running behind a corporate proxy or in restricted networks, ensure Docker has outbound access and that any required CLIs can reach their respective endpoints.
• Troubleshooting: If agents fail to connect, verify that the endpoints are correct, credentials are valid, and that the container has permission to reach external services. Check container logs for error messages and adjust configuration as needed.