A connector 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 a connector. Find it by name or under its group, and press Connect. Connecting one does not give anything access to it: an AI or a terminal reaches it only after you give it that connector and pick a level. Using your own connectors from an AI or a terminal takes Tools.
In a workspace. Open the workspace’s Connectors page and press Add a connector. 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. To begin with, everyone in the workspace can use it there, at no extra cost. Who else may use it is up to you, on your Approvals page: Connect accounts has each setting.
Each connector connects one of four ways:
| How it connects | What you do |
|---|---|
| A sign-in | Sign in on the vendor’s own page: Google, Microsoft, LinkedIn, X, Notion, Linear, Stripe and many more. Connect as many accounts as you have; a work account and a personal one are two accounts, with separate levels and separate limits. |
| Included | Nothing. GBrain holds the key for web search, page reading and research. Each use is paid from the organization’s usage credit and shows in the activity log with its cost. |
| Your key | Paste a key or a password of your own once: iCloud, Captain, Crustdata, Happenstance and X. An iCloud account takes the Apple Account email and an app-specific password Apple makes for this, at account.apple.com. |
| Your server | Give the address of an MCP server the team runs or uses. It signs in like any other, or asks for a key, or for an OAuth application you made (below). Add your own MCP server is at the foot of the list. |
Any connector with an MCP server
The list is where to start, not the limit. Any vendor that publishes an MCP server connects by its address: press Add your own MCP server, at the foot of the list or under a search that finds nothing, give the address, and sign in or paste a key if it asks. It is then a connector like the rest: an AI or a terminal reaches it only once you give it to them, at a level you pick, and a connector you connected for yourself goes into a workspace with one press, Add. The same search offers to ask us to list a missing one for everybody.
Ask the AI to add one
An AI connected to GBrain can open the same door from its side. Say “add this MCP server to my GBrain” and give it the address, and it answers with a link. Opening the link is the whole of the approval: sign in to the server there, or paste the key it asks for, or press Add for one that needs neither, and it becomes a connector on the account, already given to the AI that asked, so the next thing it does can use it. Nothing is connected by the AI itself, and a link left unopened connects nothing.
The same three ways in apply, because it is the same page: a vendor’s own sign-in, a key, or nothing at all. An address that is not an MCP server is refused with what the server answered, and a server already connected is pointed at rather than connected a second time.
Sign-ins, not a password manager
GBrain keeps the sign-in an AI uses for each connector, so the AI never sees a password or a key. It does not read from a password manager: there is no 1Password or Bitwarden connector to set up, and nothing to export from one. Each connector is connected by signing in on the vendor’s own page, or by pasting a key, once.
Every use is on the record
Each AI and each terminal has a connection of its own, so the activity record says which one used a connector, what it asked for, and when. A connector’s own Activity tab lists every use of it, whichever AI asked.
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 connector 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.
LinkedIn: posts on your own profile
Signing in with LinkedIn connects your personal profile. At Read, an AI or a terminal sees who you are on LinkedIn: your name and member id. At Read & Write, it posts on your profile as you, plain text up to 3,000 characters, public or for your connections only. A post can carry one of these: a link, a picture or video, or a post it reshares. It can also comment on a post as you, and delete a post it made. A video takes a minute or two for LinkedIn to process before the post appears. Each post and comment is sent once and is on the record, without its words. Give Read & Write only to an AI you trust to post what you approved.
LinkedIn asks you to sign in again every 60 days. When the sign-in ends, the connector says it needs reconnecting, and any post an AI tries is refused until you do, with the page to do it.
A company page is not included. Posting as a page needs LinkedIn’s partner approval, which GBrain does not have yet, so the connector reaches your own profile and nothing else. It cannot mention people, schedule a post or read your feed.
X: posts on your own account
Signing in with X connects your X account. GBrain brings its own access to X’s API, so you need no X developer account. At Read, an AI or a terminal sees who you are on X, and your own recent posts with how each did: views, likes, reposts, replies, quotes and bookmarks. At Read & Write, it posts on your account as you: plain text, one link if you give it one, and one picture or video. It can reply to a post, so a thread is a post and its replies. It can repost, take a repost back, and delete a post it made. A deleted post is gone from X for good. Each post is sent once and is on the record, without its words. Give Read & Write only to an AI you trust to post what you approved.
X charges for every post made through its API. GBrain pays X and takes it from the workspace’s credit, and the activity log shows each charge:
| Action | Price |
|---|---|
| A post | 3¢ |
| A post with a link in it, given as the link or typed into the text | 40¢ |
| A post with a picture or video | the same as the post |
| A repost | 3¢ |
| Deleting a post, or taking back a repost | 2¢ |
| Reading who the account is | 2¢ |
| Reading recent posts and their numbers | 1¢ a post |
Each X account can post, repost or delete 25 times a day. A workspace on its free start cannot post on X; keeping the workspace turns it on. X’s own limits apply too, and most accounts take 280 characters in a post.
An X account connected before November 9, 2026 posts text and links as before. To post a picture or video, connect it again once.
The sign-in stays until you disconnect it or remove GBrain on X. It cannot quote a post, schedule a post or read someone else’s timeline. Searching X posts is a separate connector, on a key.
iCloud: mail and calendar, with a password Apple makes for this
An iCloud account is connected with an app-specific password rather than a sign-in, because Apple offers no sign-in a third-party program can use for mail or for a calendar. The password is made at account.apple.com, under Sign-In & Security, then App-Specific Passwords; that entry is there only once two-factor authentication is on for the account. The connect page walks through it in four steps with a picture of each Apple screen, because that is where people stop; the fields to paste the password into appear on the last step, when you have it in your hand.
One iCloud connector covers both halves of the account. It reads mail: searching a folder, reading one message, and listing the folders the account has. It reads the calendar too: listing the calendars the account keeps, and what is on them over a window of up to a year, with repeating events worked out for the days asked about rather than answered as the day they were first written. Time zones are read as the event was written and answered in UTC. It cannot send, move or delete mail, and it cannot create, change or cancel an event.
The address has to be an @icloud.com, @me.com or @mac.com mailbox. If the Mail app on an iPhone shows a Gmail or an Outlook account underneath, that account is the one to connect, and it connects by signing in.
Changing the password on the Apple Account cancels every app-specific password, which includes this one. The connector then says it needs reconnecting, and the page for it is where a new password goes.
When a connector has you make an OAuth application 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 a connector walks you through it:
- In HubSpot, open Development, then MCP Connectors, and create an MCP connector for GBrain.
- Enter this as its redirect URL:
https://gbrain.io/oauth/mcp/callback. - 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 a connector 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 chat apps, not connectors, and no AI or terminal reaches them. GBrain in Slack has the setup.
From the terminal
A terminal can list what you can connect and what you have, and open the page that connects one. There a connector 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.
When one needs reconnecting
A vendor can end a sign-in on its own side, for instance when a password changes or access is taken back. The connector then says Needs reconnecting wherever it is listed: in Tools and on each workspace’s Connectors page. Reconnect is right beside it. It opens the vendor’s sign-in, and once that is done the same connector works again, with every level and workspace it had. Only the person who connected it can reconnect it, so a colleague’s says whose it is instead.
Removing one
Open the connector, then its Danger zone, and press Disconnect this connector. 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 Connectors page says who disconnected it, and what it already did stays on the record.
Where the connector 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 and LinkedIn offer no way to do that from here, and GBrain does not tell X yet, so the page tells you to remove GBrain in your Microsoft account, under LinkedIn’s Settings, Data privacy, Permitted services, or under X’s Settings, Security and account access.
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 connector 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 Connectors page.