zebflow 0.7.3

Reactive web automation platform — pipelines, templates, and real-time collaboration in a single binary.
Documentation
# MCP by Project

MCP access in Zebflow is project-scoped.

That matters because agents should operate with clear boundaries:

- one owner
- one project
- one capability envelope

## Why this is important

It makes agent access:

- easier to reason about
- easier to revoke
- easier to audit
- cheaper to operate safely

For the deep operational reference, see `help("platform/agent")`.