Skip to main content
Bridge gives AI agents a single interface to read structured context from your storage backends. Instead of writing and maintaining different SDK integrations for files, databases, and future providers, you configure Bridge once and call the same CLI everywhere.
One CLI. Any storage. Every agent. Bridge is open source, local-first, and designed to return machine-readable JSON on stdout so agents can consume it directly.

​
Why Bridge exists

AI agents need context, but every backend speaks a different language. A filesystem read does not look like a Postgres query, and switching backends usually means rewriting the integration. Bridge sits between your agent framework and your data so you can standardize how context is listed, read, and passed downstream.
Bridge runs outside the token loop. Instead of routing every storage read through custom SDK code or a tool server, your agent can call bridge, read JSON, and keep moving.

​
How Bridge works

  1. Create a bridge.yaml file in your project.
  2. Connect one or more providers.
  3. List available context with bridge ls.
  4. Read structured data with bridge read.
bridge init
bridge connect file://./docs --as files
bridge connect postgres://localhost:5432/mydb --as db

bridge ls --from files
bridge read README.md --from files
bridge read users/42 --from db

​
Available today

  • Filesystem provider for files and directories
  • Postgres provider for tables and rows
  • Structured JSON output with metadata
  • Cross-platform binaries for macOS, Linux, and Windows
  • Shell completions for bash, zsh, fish, and PowerShell

​
Where Bridge is going

Bridge starts as a local-first CLI for agent context. Over time, Bridge Cloud will make it possible to share permissioned context slices across agents, teams, and organizations while keeping your data in your own backends.

​
Next steps

Concepts

See how Bridge fits alongside MCP and A2A in the broader agent stack.

Quickstart

Install Bridge and connect your first provider.

Contributing

Help improve the open-source CLI with providers, fixes, tests, and technical docs.

View the source

Explore the CLI, roadmap, and release history on GitHub.