Cloud/Connectors/Credentials
Credentials
Where your connector gets its identity: encrypted fields with show and hide, a Test Connection verdict in one click, OAuth when the provider supports it, and the three promises written at the bottom of the screen.
Credentials are the bridge between your account and the outside service: the token that lets the connector read your repos, send your emails, query your database. The Credentials tab is where that bridge is built, and the screen introduces itself exactly as it is: "Connect your account so AI agents can use this Connector."
Credentials
Connect your account so AI agents can use this Connector.
Active Credentials Saved
Credentials for this server are active. Entering new values below will securely replace the existing ones. Leave blank to keep current credentials.
A fine grained token with repo and issues scopes. Used for every request the agents make.
The mockup is the real editor in update mode: click the eye to reveal or mask the token, hit Test Connection to see the verdict banner, and save. Nothing leaves this page.
Encrypted by default, hidden by default
Every sensitive field carries two badges: Required, so you know it cannot be left empty, and Encrypted, with a lock: "Your credentials are encrypted at rest and in transit." The value itself starts masked (••••••••••••) with an eye button to reveal it for the two seconds you need. When a connector is already configured, the fields stay masked even in edit mode: entering new values securely replaces the old ones, and leaving them blank keeps what works. The console says it in green at the top: "Active Credentials Saved."
Test Connection: the verdict in one click
The Test Connection button asks the connector to prove itself, and the answer comes back as a color coded banner with three possible verdicts:
- Connected Successfully (emerald): the credentials work.
- Credentials could not be verified (amber): the provider did not confirm either way; try again with the refresh button.
- Connection Failed (red): something is wrong, with the provider's own message quoted below.
No more saving and praying: you know the state before you move on.
OAuth, when the provider supports it
Connectors that support OAuth show an OAuth Authorization card instead of (or after) the fields: a Connect with {provider} button opens the provider's consent popup, and the card comes back with "Connected to {provider}", an Active badge and the account email. If the authorization expires, the card turns amber with Reauthorization required and a one click Reconnect. Disconnecting asks for confirmation first.
Remove is a decision, not a slip
Remove Credentials sits apart in red, and it does exactly what it says: the stored credentials are deleted, the green block disappears, and the connector stops working until new credentials are saved. Nothing is hidden or half-done.
Free plan and the two step finish
Credential setup is a paid feature: on the Free plan the save button becomes Unlock setup, the console's upgrade call to action. On a paid plan, saving continues into the second step: Vinkius generates your first Connection Token automatically and hands you the MCP Connection URL and the token, ready for the Dashboard and your AI clients.
The three promises
The screen ends with its own guarantees, written on a green footer strip: Encrypted Storage (encrypted at rest and in transit), Never Shared (never shared with third parties) and Full Control ("Revoke or update credentials at any time."). That last one is the whole relationship in a sentence: your credentials, your switch.