AI native · MCP and CLI
AI can ask. You stay in control.
Connect Codex, Claude Code or your terminal to your team workspace. Find the right account, organise access requests and check progress without copying credentials into a chat.
Setup required. Connected access has not yet been verified for general use. Check availability.
From request to human review
- 1
Find account information
A scoped key permits account metadata lookup. Metadata can still be sensitive: grant only the access needed.
- 2
Ask a person to review
MCP or CLI creates an access request. An authorised person approves or denies it.
- 3
Check the result
The assistant receives request status. Passwords, codes and encryption keys stay outside the assistant.
Helpful assistants. Human decisions.
Agents never receive passwords, 2FA setup secrets, generated codes, encrypted content or encryption keys.
People approve or deny access. MCP and CLI can request a review and check its status; they cannot make the decision or retrieve the secret.
Connect in three steps
- Create a scoped API key in workspace Settings.
- Configure your MCP client or CLI using protected secret storage. Never paste the key into an AI conversation.
- Start with account information, then enable approval requests only when needed.
AI connections require workspace configuration. Check current availability before relying on a connected workflow.