Tools

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.

• BROperates like a humanBrowserA web product with no MCP server, operated the way a person would: a browser, on the sites you allow.View setup →
• GIIntegratesGitHubIssues, pull requests, reviews and checks, through GitHub's own hosted MCP server.View setup →
• MEIntegratesMetabaseQuestions, dashboards and queries, through the MCP server built into your own Metabase, connected with OAuth.View setup →
• OUIntegratesOutrankWriter questions for scheduled articles, through Outrank's MCP server, which you host.View setup →
• POIntegratesPostmarkTransactional email from your own Postmark account, through Postmark's MCP server, which you host.View setup →
• SEIntegratesSentryIssues, events and traces, through Sentry's own hosted MCP server, connected with OAuth.View setup →
• SLIntegratesSlackMessages, channels, search and files, through Slack's own hosted MCP server.View setup →
• WEOperates like a humanWebThe public web, read directly: a page as text, a sitemap as a list, a URL's text or JSON. Nothing to connect.View setup →
• +Your toolUsing a system with no guide here? Write up how you connected it.Add a tool →