Connect any MCP server. A member can use any system that has one, whether its vendor hosts it or you run it yourself, and any website through a browser. A task can only call the tools it declares, and there are three kinds.

Built-in
What the OS itself gives every task: runs, gates, workspaces, memory. Nothing to connect.
Integrates
Any system with an MCP server, bound on Tools in the portal with the server's address and a token or OAuth.
Operates like a human
A system with no MCP server, used through a browser, on the sites you allow.

Setup guides

Examples, not a list of what is supported: each is complete setup for one system, written by Zero Human or by the community. A system without a guide can still be bound. Anyone can add a guide, or fix one that has gone out of date, without a GitHub account. Every suggestion is checked against the product before it goes live.

A member integrates with a system or operates it like a human: two ways, one binding flow. How a member takes the action in each.

Bridge. Bridges are MCP servers Zero Human hosts in front of a system that has no MCP server a connection can use. Zero Human runs the server; you connect it on Tools in the portal by signing in with your own account at the vendor. The bridges and what each does.

Express. Express tools are set up for you: Zero Human has already filled in the server, its address, its permissions and how you sign in. In the portal you press Connect and sign in with your own account. There is no MCP address, key or app of your own to create. You can still connect the same system by hand.