Connected apps
Sign in with Zero Human from an MCP client instead of pasting a token, and revoke the app later.
Planned. What this page describes is not built yet.
Signing in
An MCP client that supports sign-in, such as a custom connector in Claude or ChatGPT, connects to your enterprise's MCP server without a token. Adding the server starts a sign-in with Zero Human, and you approve the connection on a consent screen:
- the enterprise it connects to;
- the member it acts as, one of that enterprise's AI team members;
- what it may do, in the same
<resource>:<level>scopes as an API token, capped at what you hold yourself.
Only a person who can sign in to the portal can approve a connection, and only for an enterprise they belong to. A person with a mailbox of their own finds the server address, the steps for Claude and for ChatGPT, and the apps they connected on Account.
Your own mail
One scope is yours rather than the enterprise's: mail, your own mailbox
(People and access). Tick Read on it and the app can list and read
your mail, as you and nobody else, with os.my_mail_list, os.my_mail_read and os.my_mail_attachment, and see
the one-click buttons your inbox offers (os.my_mail_actions). Tick Write and it can also reply, forward and
send from your address, as you, with no approval step (os.my_mail_reply, os.my_mail_forward, os.my_mail_send),
keep your inbox in order with labels and a handled state (os.my_mail_set_label, os.my_mail_set_handled,
os.my_mail_set_many), delete a mail for good (os.my_mail_delete) and press one of the buttons, which starts that
task over your own mailbox (os.my_mail_start_action). Either is yours to give whatever else you hold in the
enterprise, and no API token can ever hold it. The consent screen says so beside the choice.
Revoking
Settings → Connected apps lists every connection: the app, who approved it, the member it acts as, its scopes, and when it was last used.
- Revoke refuses the app's next request. The connection stays listed, revoked, so the record outlives it.
- Scopes are not edited here. Changing what an app may do is a new sign-in by the app, which you approve again.
With a token instead
A client that cannot sign in connects with an API token: Connect a client. An enterprise token
acts for the enterprise, not for you, so it never reaches your mail. For your mail alone, issue a
token of your own on Account: it is you, for /v1/mail and the
os.my_mail_* tools, and nothing else.