Connections is where you give your digital humans access to everything external they need to act: one-click apps, MCP servers, or your own APIs. Anything you connect here becomes available both for chatting with a digital human and for the Use a tool steps in your workflows.
The three tabs
| Tab | What it's for |
|---|---|
| Your connections | Everything you've already connected — apps, MCP servers, HTTP tools — with its status and a button to manage or disconnect it. |
| Browse | The catalog: apps and MCP servers Brain has already verified, ready to connect in a couple of clicks. |
| Tool Studio | Where you build: connect your own MCP server or create a custom HTTP tool over any API. |
Three ways to connect a tool
| Type | What it is | Use it when |
|---|---|---|
| Catalog app | One-click sign-in — Brain already manages the credentials. | The app you need is already in the catalog. See Connect a catalog app. |
| MCP server | A server that exposes tools following the Model Context Protocol standard. | The service already publishes an MCP server — from the curated catalog or your own. See Connect an MCP server. |
| Custom HTTP | A tool you define over any REST API. | You only have an HTTP API, no MCP. See Create a custom HTTP tool. |
Create with the assistant
Tool Studio includes an assistant that understands natural language, curl commands, OpenAPI, and MCP. It guides you step by step and presents every change as a proposal that you must approve before it is applied. See Use the Tool Studio Assistant.
Connecting isn't the same as granting access
Connecting an app, an MCP server, or an HTTP tool makes it available in Brain. You then choose which digital humans can access it. Each tool's execution policy — allow, require approval, or block — is global and shared by all of them. See Permissions and access.