Tools and MCPs

Manage Credentials in Visual Builder

Copy page

Credentials are used to authenticate MCP servers.

The credentials page allows you to add credentials to your MCP servers.

Adding a credential

Make sure your Visual Builder is running (if you haven't set it up yet, see Quick Start). Navigate to the Credentials tab in the left sidebar, click "New credential", and select "Bearer authentication".

  1. Fill in the required credential details:
FieldDescription
NameA descriptive name for your credential (e.g., "production-api-key")
API keyThe authentication token or API key for the service
  1. Optionally, configure additional settings:
FieldDescription
MetadataAdditional headers to include with authentication requests (e.g., User-Agent, X-API-Key). Only available for Nango Store.
Credential storeWhere to securely store the credential. Choose from available stores (Nango Store or Keychain Store)
Link to MCP serverOptionally associate this credential with a specific MCP server that does not have a credential configured
  1. Click "Create Credential" to save the credential.

To use the credential in an MCP server, you can reference it when creating or editing the MCP server. See the MCP Servers page for more information.

Managing OAuth app configurations

OAuth providers support multiple app configurations per provider. When you navigate to add an OAuth credential for a provider that already has app configurations, an interstitial page displays your existing configurations.

Each configuration appears as a selectable card showing the app name and masked Client ID and Client Secret for identification. Select a card to create a new credential using that app configuration, or choose to add a new one.

A three-dot menu on each card provides options to:

  • Edit — Update the OAuth app credentials
  • Delete — Remove the app configuration (with a confirmation dialog)

Editing OAuth app credentials

Select Edit from the three-dot menu to update an app configuration's Client ID or Client Secret.

Warning
Warning
Updating OAuth app credentials invalidates all existing connections that use that configuration.

Viewing credential details

On the credential edit page, OAuth credentials display an App configuration section showing the linked OAuth app's masked Client ID and Client Secret.

Auth types display as human-friendly labels — for example, OAuth 2.0, API Key, or App authentication — instead of internal identifiers.