MCP credentials

You can use these credentials to authenticate the following nodes:

• MCP Client Tool

Prerequisites

You need an MCP server that supports OAuth2 authentication.

Supported authentication methods

• OAuth2

Using OAuth2

This credential extends n8n's generic OAuth2 API credential, with two additional fields for MCP's authorization flow:

• Use Dynamic Client Registration: Turned on by default. When on, n8n automatically registers itself as an OAuth2 client with the MCP server (RFC 7591), so you don't need to manually create an app or paste in a Client ID and Client Secret. Turn this off if your MCP server doesn't support Dynamic Client Registration, or if you already have a Client ID and Client Secret from the server's own developer settings. In that case, fill in the standard OAuth2 fields (Authorization URL, Access Token URL, Client ID, Client Secret) as you would for any generic OAuth2 credential.

• Resource URL: Optional. The exact protected resource URL required by the MCP server. Leave this empty to let n8n discover it automatically from the server.

Having trouble with Dynamic Client Registration?

If you see errors related to a mismatched or invalid redirect URI during the OAuth2 flow, double-check that your MCP server's Dynamic Client Registration endpoint is configured to accept n8n's OAuth Redirect URL exactly as shown in the credential.