Add the server
Add Keebai to the client’s MCP configuration with the URL and noAuthorization header. The exact file and key names belong to each client; these are the usual shapes.
401 that points to the sign-in metadata. The client then opens your browser at accounts.keebai.com. Some clients do it on their own; others show a Sign in or Authenticate action in their MCP panel. If yours does not, check its documentation for how it handles OAuth on remote servers.
If the client has no OAuth support, connect it with a Personal Access Token instead.
What you see when you connect
1
Sign in at accounts.keebai.com
Sign in with your email and password, and your second factor if you have one. If you are already signed in, this step is skipped.
2
Choose the company
If you belong to more than one company, pick the one the app will work on. A connection always belongs to one company.
3
Approve the permissions
Permissions come in six groups. You only see as available the groups your Keebai role allows; the company owner and superusers can grant all of them. Untick any group you do not want the app to have.
4
Back to the app
Click Allow access and the browser returns to the app, already connected.