Skip to main content
The sidebar label is App credentials (route Auth Config). These are project-level secrets — OAuth client id/secret or API keys — that agents and MCP use when end users connect. They are not the same as Connections: Page help in the UI: App credentials hold project-level secrets (OAuth app, API keys). Connections on the Connections page are per end user.

​
Create app credentials

1

Open App credentials

Go to App credentials. Confirm the correct project is selected.
2

Create

Click Create app credentials. Pick a toolkit that needs project credentials (for example Gmail OAuth). Managed cloud auth may be created automatically when users connect for some toolkits.
3

Fill provider fields

Enter the values the toolkit asks for (client id/secret, API key, …). Save.
4

Connect end users

Open Connection under each end user and complete OAuth. Do not ask end users for client secrets — those stay in App credentials.
If a connect flow says credentials are missing, create or bind App credentials for that toolkit first, then retry.

​
Delete

Deleting credentials cannot be undone. The UI warns that all connected accounts under those credentials will be deleted, and agents or MCP servers bound to them will stop until you bind new credentials. Confirm by typing DELETE when prompted.

​
Tips

  • Search by name, toolkit, or scheme when the list is long.
  • MCP Install & Config and Smart-mode toolkit binding can point at these credentials — see MCP in the dashboard.
  • For multi-tenant apps, keep one set of App credentials per toolkit and many Connections under different end users.

​
Developers

API and SDK: Auth configs. Link flow: Connected accounts.