Bridges
The Zero Human bridges: what each reads, what it writes, and how to connect it.
A bridge lets your team's tasks use a system that has no direct connection of its own.
Members call tools through MCP, the Model Context Protocol: a standard way for an AI to call another system's tools. Many systems offer an MCP server of their own, which you connect directly. A bridge is an MCP server in front of a system that has no hosted MCP server of its own, or whose sign-in a connection cannot use. A member reaches a bridge as it reaches any other tool: through a connection on Tools in the portal, signed in with your own account at the vendor. In a run, a member reaches it only through the tools the task names.
The bridges
- Google Search Console and GA4: read-only. It reads Search Console and GA4, and writes nothing. From Search Console it reads search performance, index status and sitemaps; from GA4, reports and realtime data. Zero Human hosts it, and you connect it by signing in with Google.
- Postmark: reads sent messages and templates, and writes: it sends email and changes templates. It also reads bounces, suppressions and delivery statistics, and changes suppressions and webhooks. You run it yourself, in front of Postmark's own server.
Each bridge's page names every tool it serves, under the name a task uses, and says what it reads, what it writes, who signs in, what waits for you, and its limits and cost.
What every bridge has in common
- Your own account. A bridge signs in to the vendor as your account, and reaches only what that account can. No account, key or rule of one enterprise is shared with another.
- In a run, only the tools the task names. A tool the task does not name is refused, whatever the connection allows. A connection on a member, team, role or the enterprise also reaches the chat of every member it covers, with every tool the bridge serves; a connection on a task never reaches chat.
- In a run, a write waits only when the task gates it. To approve each change before it is made, gate the tool that makes it. See Gates and tool scopes. In a chat, a tool its server does not mark read-only asks you before it runs, unless you chose Always allow for that member and tool.
- No Zero Human charge of its own. A bridge's calls happen inside runs, and your plan counts those runs as it counts any other. Any charge the vendor makes is on your own account with that vendor.
- Who hosts it changes what running it costs. A bridge Zero Human hosts, as it hosts Google's, has nothing for you to run or pay for. A bridge you run yourself, as you run Postmark's, also costs whatever the place you host it charges.
A system whose vendor hosts an MCP server a binding can use needs no bridge: you bind the vendor's own server, as the guides in the Tools directory show.