Create an MCP Connector with OAuth 2.1
Create an MCP Connector with OAuth 2.1 for connecting to external systems or applications that support MCP.
시작하기 전에
Role required: sn_mcp_client.admin
이 태스크 정보
OAuth 2.1 provides the most secure and flexible authentication for MCP connectors. If your MCP server supports it, select OAuth 2.1 as the authentication method. You can choose between Dynamic Client Registration, where the server auto-populates client details, or Manual Client Registration, where you provide the client details yourself.
프로시저
-
On the form, fill in the fields.
표 1. System Details Field Description Server name Name of the MCP server. For example, Linear MCP server. System Search for the external system you want to integrate. Add system (Optional) Click the 
icon to add an external system. For more information, see Create external systems.주:If you already have an existing system, you can use that system for the MCP connector.Connection name Select New connection and enter a name to uniquely identify the connection. For example, Linear Connection. 표 2. Connection Configuration Field Description Endpoint name This field is auto-populated with the Connection name. Endpoint URL Connection URL for the MCP server. Authentication Method Select OAuth 2.1. Select the registration type based on your MCP server's capabilities.
표 3. Manual Client Registration Field Description Authorization method Select the grant type to be used for requesting tokens from the authorization server. - Authorization Code: A system-generated code used for granting access to an application or resource.
- Client Credentials: Access token provided by the administrator to access the application directly.
Client ID Client ID of the OAuth provider. Client Secret Client secret of the OAuth provider. Client Authentication Specifies how the client credentials are sent to the OAuth token endpoint when requesting an access token. - Client Secret Post: Sends the client ID and client secret in the request body as form-encoded parameters when calling the token endpoint.
- Client Secret Basic: Sends the client ID and client secret in the HTTP Authorization header using Basic authentication when calling the token endpoint.
Access permissions Select the required scopes. These scopes determine the permissions of this OAuth client. OAuth Auth URL URL of the OAuth authorization server. OAuth Token URL OAuth server endpoint used to obtain access tokens. Token revocation URL OAuth server endpoint used to revoke previously issued tokens. 표 4. Dynamic Client Registration Field Description Authorization method Select the grant type to be used for requesting tokens from the authorization server. - Authorization Code: A system-generated code used for granting access to an application or resource.
- Client Credentials: Access token provided by the administrator to access the application directly.
Client Authentication Select how the client credentials are sent when requesting tokens from the authorization server. - Basic Authorization Header
- Request Body Parameter
- Private Key Jwt
Access permissions Select the required scopes. These scopes determine the permissions of this OAuth client. Authorization URL URL of the OAuth authorization server. Token URL OAuth server endpoint used to obtain access tokens. Token revocation URL OAuth server endpoint used to revoke previously issued tokens. Client registration token Token used to authenticate requests to the OAuth client registration endpoint. Value Token for dynamic client registration. Leave this value blank if the server supports unauthenticated registration. -
Click Save.
For example:
You are redirected to the third-party page requesting authorization for the MCP client.