Grok and Grok Bot
Grok and Grok Bot work with a bearer token: you give them 0bridge's URL and a token instead of signing in through a consent screen. Level: bearer token. Last checked 2026-10-01.
Last updated
Set it up#
Mint an app token on the dashboard, then give Grok the URL and the token.
- Open the dashboard → Settings → Devices → New app token.
- Name it
Grok. The defaults are the safe ones: your services' tools, no history, no agent control, valid for 90 days. Confirm it's you when asked. - Copy the token. It is shown once.
- Where Grok asks for the server, enter the URL, and where it asks for a header or token, enter the token as a bearer token.
https://0bridge.dev/mcp
Authorization: Bearer <your token>Grok Bot has no URL field: it registers a server through chat or the marketplace. However your version of the product takes them, a URL and a token are the two values it needs. The exact screens change quickly and we haven't walked through them on this date, so follow what the product shows.
Does Grok Bot have a shell?#
We don't know yet. The token above is how Grok Bot reaches 0bridge's tools. Whether it also runs shell commands on a computer where the setup for agent computers could run is unverified, and we don't say it does.
What the token can do#
The default scope is the one a bearer-only client should have: your connected services' tools, nothing from your coding-session history, no agent control, no secrets. You can narrow it further (read-only tools) when you create it.
Revoke it#
Settings → Devices lists the token; revoke it there and it stops working at once. It also stops by itself after 90 days.