New capabilities of the brain
Connect a service
- In the brain, open the Connections tab and click Add connection. Ready ones include Notion, Linear, Jira and Confluence, Figma, Canva, Stripe, Sentry, ClickUp and GitHub; any other service can be added by its MCP server address.
- Choose whose account is used:
- Personal account: everybody signs in on their own and the service sees who does what.
- Shared account: a manager signs in once, for example with a service account, and everybody with the role uses it.
- Click Sign in. The service's page opens (like
/mcpin Claude Code), and after signing in it is done. Services without a sign-in get a key (API token). - In the role (Sharing → role → Connections), tick which roles get the connection.
Sign-ins and keys never get into the brain or onto computers: Claude Code calls the service through the onlybrain gateway, which adds the sign-in and renews it by itself. A person leaving or a change of role disconnects everything in one place.
The process
A capability is more than a connected tool. It also needs rules: where to read from, where to write, what it may prepare and what it may actually do.
- Describe a concrete result: a morning overview of meetings, not "calendar" in general.
- Set the source and the target place in the brain.
- List the steps that need confirmation. Sending an e-mail, changing a meeting or an invoice must not happen silently.
- Have an agent or a skill created (see step 2), together with a connection guide. Never store access keys in the brain.
- Try it on a harmless example first.
Example prompt
I want the brain to prepare an overview of today's meetings every morning.
For each one, find the client or project in the brain, summarize the last
agreement and list the open tasks. Suggest an agent and a skill for Google Calendar.
Don't change anything in the calendar and don't write to anyone without my explicit
confirmation. Secrets must not be stored in the brain. First show me the steps
and the permissions needed.Safely
- Start with read-only access. Add writing when it is really needed.
- Write into the instructions what to do on an error or incomplete data: stop and ask.
- Every now and then, go through unused permissions and revoke them at their provider.