An MCP server exposes a set of tools following the Model Context Protocol standard. You can connect one from Brain's curated catalog in a couple of clicks, or federate your own server from Tool Studio.
From the catalog
- Open Connections → Browse and find the server you need under Tools — these are MCP servers Brain has already verified and added to the catalog.
- Press Add connection.
- Depending on the server: some connect instantly with a single piece of information (for example, your store domain), no sign-in required; others take you through an OAuth sign-in to authorize access.
Find an option with the assistant
If the service is not in the catalog, open the Tool Studio Assistant and describe what you need. It can search public internet sources and distinguish official, community, and unverified options. You do not need to wait for approval from the Brain team to use a result, but you are responsible for evaluating the source and permissions of any external server before connecting it.
Your own server
If the service you want to integrate publishes its own MCP server, federate it from Connections → Tool Studio → MCP server:
- Tool name — how you'll identify it in Brain.
- MCP server URL — for example
https://your-mcp-server.com/mcp. - Choose the authentication method:
- Token / none — paste an optional access token; it's stored encrypted and sent as a bearer token.
- OAuth — Brain registers a client automatically and sends you to the server to authorize access. If the server doesn't support automatic client registration, you can paste the Client ID and Client Secret you pre-registered with the provider yourself.
- Accept the responsibility notice and press Connect (or Connect with OAuth).
Brain verifies the endpoint and lists the available tools before connecting.
Manage a connected server
Every server shows up under Your connections → Manage shows its status (Active or Discovery failed), the connection date, and the tools Brain discovered. If discovery fails, open Connection settings to correct the URL or credentials and retry without deleting the connection or losing its assignments.
From there you also control permissions and per-digital-human access to the discovered tools.