Applications

An application is something you have connected: a Google account, a Notion workspace, a search key. It belongs to you, not to any one AI, and it is the thing an AI, a terminal or a workspace is given permission to reach.

Connecting one

There are two places to connect one, and both end the same way: you sign in, or paste a key, in your browser.

For yourself. Open Tools, then Add an application. Find it by name or under its group, and press Connect. Connecting an application does not give anything access to it: an AI or a terminal reaches it only after you give it that application and pick a level. Using your own applications from an AI or a terminal takes Tools.

In a workspace. Open the workspace’s Tools page and press Add an application. An account you already connected for yourself is one press, Add; anything else signs in first. It goes into that workspace at once, on, and what the workspace does with it is yours: it shows on your Activity. Everyone in the workspace can use it there, at no extra cost.

Each application connects one of four ways:

Microsoft: mail, calendar and OneDrive

Signing in with Microsoft connects Outlook mail and calendar. OneDrive is asked for on its own, so a mailbox that only wants mail is never asked for its files: open the Microsoft application and press Connect beside OneDrive. Microsoft asks again, for the same account.

An AI edits a Word document in OneDrive the way a colleague does. Each change is a tracked change and each note is a comment, both by GBrain, so you accept or reject them in Word. The rest of the document keeps its formatting. If someone saved the document after the AI read it, GBrain writes nothing, and the AI reads it again.

OneDrive’s search can miss files for hours, Word documents most, so an AI that finds nothing lists the folder instead. Files someone else shared with you are not reached yet.

When an application has you make one for GBrain

Some vendors’ sign-ins don’t let GBrain register itself, so each person makes an OAuth application for GBrain in the vendor’s own settings. HubSpot is one: it calls it an MCP connector. Its page in Add an application walks you through it:

1. In HubSpot, open Development, then MCP Connectors, and create an MCP connector for GBrain.
2. Enter this as its redirect URL: https://gbrain.io/oauth/mcp/callback.
3. Paste its client ID and client secret, and press Sign in to HubSpot.

HubSpot’s own sign-in page opens with that connector, and from then on it renews and disconnects like any other sign-in. GBrain keeps the client secret encrypted on our servers with the rest of the sign-in, sends it only to the address the page names (mcp.hubspot.com), and no AI and no workspace receives it. When you disconnect, it is deleted once HubSpot has been told.

GBrain only takes a client secret for an application it lists, because it can’t check where another server would send it. If you add your own MCP server and it can’t register GBrain, the page says so and offers a way to ask us to list it. A server that gives you a key works today: the same page takes one.

A few vendors haven’t approved GBrain’s sign-in yet. Their page says so and offers a way to ask us about it instead.

Slack and Telegram

Slack and Telegram are places the team talks to a workspace, and it answers there, so a workspace connects them itself: open Messaging, under Integrations in its sidebar, and pick one. They are not applications, and no AI or terminal reaches them.

From the terminal

A terminal can list what you can connect and what you have, and open the page that connects one. There an application is a tool, connected or not. It never takes a key or a sign-in, and never grants anything: connecting always finishes in the browser.

$ gbrainio tool ls --available        # every one you can install
$ gbrainio tool ls --available -w 7   # what workspace 7's Install page offers you
$ gbrainio tool show                  # every one on your account, and where
$ gbrainio tool show notion           # one in full: what it does, how it connects, your copies
$ gbrainio tool install notion -w 7   # open the page that installs Notion in workspace 7

Set up a terminal has what each one prints.

Where the keys live

On our servers. An AI never receives the key, and neither does the workspace. Every action is brokered: the AI asks GBrain, GBrain checks what that AI is allowed to do, makes the call itself, and hands back the result.

That is what makes the levels real. If a level could be bypassed by an AI holding the key directly, the setting would be decoration.

Removing one

Open the application, then its Danger zone, and press Disconnect this application. The page lists what will stop before you confirm: each AI and terminal that has it turned on, by name, and each workspace it is in, with the other people there who lose it. Confirm, and all of it stops at once. The workspace’s Tools page says who disconnected it, and what it already did stays on the record.

Where the application has a sign-in, GBrain then tells the vendor its access is over. The page says when the vendor has confirmed, and keeps trying until it does. Microsoft offers no way to do that from here, so the page tells you to remove GBrain in your Microsoft account.

Connecting it again does not put it back where it was: it starts turned off everywhere. GBrain then shows each AI, terminal and workspace it was turned on in, with the level it had, and one press puts it back in each. A Google or Microsoft account, or a public server, comes back as the same application with its history. A server you sign in to comes back as a new one.

To take one out of a single workspace and keep it on your account, use Remove on its card on that workspace’s Tools page.