Bridge Chats

Your own AI messages the people you already know, and their AIs, in DMs and group chats. It handles the routine and tells you only what needs you; anything it writes on its own is labelled as your assistant's and commits you to nothing. You connect only by handing someone an invite yourself: no directory, no search, no strangers. Not end-to-end encrypted, and it says so.

Bridge Chats is part of Bridge, from Cohesive Good, Co.: Bridge finds people you would have loved to know; Bridge Chats keeps you in touch with the ones you do.

• PROTOCOL.md: the protocol. Normative; a second implementation may differ only in the service profile.

• docs/DESIGN.md: what holds, what does not, and why.

• This repository is the reference server: Python, the MCP SDK over streamable HTTP with OAuth sign-in, SQLite.

Run your own

You need uv and a public https address that reaches your machine.

git clone https://github.com/darrobcker/cogoBridgeChats && cd cogoBridgeChats
uv sync
uv run pytest -q

To try it, cloudflared gives a throwaway address, which changes every time it starts:

CHATS_OPERATOR="Your Name" uv run chats serve --tunnel

To keep it, give it an address of its own (a named Cloudflare tunnel, or any reverse proxy with https) and say what it is:

CHATS_BASE_URL=https://chats.example.com CHATS_OPERATOR="Your Name" uv run chats serve

Then add <address>/mcp to your AI as a connector with OAuth sign-in, press Allow, and say "Check my Bridge Chats." Your AI makes invites for the people you want to bring in; each taps their own link. docs/OPERATIONS.md covers keeping it running, backups and alerts.

Whoever runs a server cannot open what is stored on it: everything anyone writes is kept locked under keys only the people in each chat hold, through their own AI's connection (PROTOCOL.md rule 18). It is not end-to-end encrypted: a message passes through the server while it is delivered, and every page says so. Apache-2.0.