Agent Bridge

Agent Bridge

Shared context layer for heterogeneous AI agents. Connects always-on assistants, coding agents, and any other AI agents through a simple post/get/ack protocol backed by Supabase.

The Problem

You have multiple AI agents working on the same machine or project: an always-on assistant (like OpenClaw), a coding agent (like Claude Code), maybe more. Each operates in its own silo. When one makes progress, the other has no idea. You end up manually relaying context between them.

Agent Bridge solves this with a shared context bus: agents post updates, read what others posted, and acknowledge what they've seen.

Architecture

┌──────────────────────────────────────┐
│     Supabase  (shared_context)       │
└──────────┬──────────────┬────────────┘
           │              │
       HTTPS REST     HTTPS REST
           │              │
   ┌───────┴───────┐ ┌───┴──────────────┐
   │  MCP Server   │ │  CLI (bash+curl)  │
   │  (TypeScript) │ │  agent-bridge     │
   └───────┬───────┘ └───┬──────────────┘
           │              │
   ┌───────┴───────┐ ┌───┴──────────────┐
   │  Claude Code  │ │  Any agent with   │
   │  Cursor, etc. │ │  shell access     │
   └───────────────┘ └──────────────────┘

Both interfaces hit the Supabase REST API directly. No shared filesystem, no local database, no sockets. Works from any machine with internet access: laptop, Raspberry Pi, VPS, CI runner.

Quick Start

1. Create a Supabase project

Go to supabase.com and create a free project. You'll need:

• Project URL: https://your-project.supabase.co
• Anon key: Found in Settings > API

2. Run the database migration

In the Supabase SQL Editor (or via CLI), run everything in [sql/setup.sql](sql/setup.sql). This creates:

• The shared_context table with indexes
• The optional atrib_receipt_id column for signed bridge-write receipts
• Row-level security policies
• The ack_context RPC function for atomic acknowledgments

3. Create the config file

mkdir -p ~/.agent-bridge
cat > ~/.agent-bridge/config  ARRAY['agent-a', 'agent-b'];

Monitoring

Use the CLI to check health:

agent-bridge status

Use Supabase dashboard to monitor table size and query performance.

Adding new agents

No schema changes needed. Just pick a unique agent name and start posting/reading. The unacked_by filter automatically works for any agent name.

Adding new categories

Categories are free-form text: no schema change needed. Just start posting with a new category string. Update your agent instructions to document what the new category means.

License

MIT

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: creatornader
• Source: creatornader/agent-bridge
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.