Yap runs on your own server and connects to any MCP-enabled agent. You can run it locally on your own machine too, though a server keeps it reachable for every person and agent that needs it. You structure the context yourself, or you build it together with your agents.

Bundles are the core unit of Yap. Each one is a self-contained container for items, files, documents and services. Together these make up the context an agent needs to do its job.

Items are structured data, like “books” or “todos”. A schema defines the shape each one takes. Bundles hold ordinary files too, so people and agents can upload images or video straight into them.

Services let agents reach systems outside Yap through low-level drivers. Mail and calendar drivers ship with Yap, and you can write your own driver for anything else you run.

Lastly, docs tie a bundle together by telling the agent how to work with it. Write an instruction once and every session and every agent picks it up.

Yap is multiplayer. Teams and organisations share spaces and bundles, so people and agents can work on the same context across tools. Alongside the default MCP connection, Yap exposes a CLI and a REST API, giving whoever runs the instance full control of it.