Model Context Protocol connectors › Build integrations with connectors › Connect › Workflow Data Fabric

Release: Australia · Updated: 2026-06-05 · Official documentation · View source

Client registration using custom connector

Define a custom connector by providing your own MCP endpoint URL and authentication configuration if the registry does not contain a connector for the system you need.

Before you begin

Role required: wdf_builder or admin.

About this task

Use a custom connector in the following situations:

The third-party system exposes an MCP-compatible endpoint, but no certified or community connector exists in the registry for it.
You are connecting to an internal or proprietary system within your organization that is not listed in the registry.
You need to override the endpoint URL or authentication settings of an existing registry connector for a specific environment or configuration.

Custom connectors support both manual and dynamic client registration, depending on the capabilities of the target system. Custom connectors are scoped to the instance and are not added to the shared MCP registry.

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.

Before you begin

Role required: sn_mcp_client.admin

About this task

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.

Procedure

Navigate to All > Workflow Data Fabric > Connect Hub.
Click Create and select Model Context Protocol.

The list of all available MCP connectors is displayed.

Image omitted: custom-connector.jpg
3. Click **Create a custom connector**.

On the form, fill in the fields.

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 Image omitted: icon-plus.png Plus icon. icon to add an external system. For more information, see <a href="../connecthub-create-external-systems/">Create external systems</a>.<strong>Note:</strong> If you already have an existing system, you can use that system for the MCP connector.</td></tr><tr><td> Connection name	Select New connection and enter a name to uniquely identify the connection. For example, Linear Connection.

|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.

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.

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:

Image omitted: connect-hub-mcp-connector.png
Example authorization request for Linear MCP connector

You are redirected to the third-party page requesting authorization for the MCP client.

Click Approve.

The MCP client for your application is created and appears in the Model Context Protocol list.

Create an MCP Connector with API Key

Create an MCP Connector with API key for connecting to external systems or applications that support MCP.

Before you begin

Role required: sn_mcp_client.admin

About this task

Use API key authentication when your MCP server requires a static key for authorization. Obtain the API key from your third-party application before configuring the connector.

Procedure

Navigate to All > Workflow Data Fabric > Connect Hub.
Click Create and select Model Context Protocol.

The list of all available MCP connectors is displayed.

Image omitted: custom-connector.jpg
3. Click **Create a custom connector**.

On the form, fill in the fields.

Field	Description
Server name	Name of the MCP server. For example, Figma MCP server.
System	Search for the external system you want to integrate.
Add system \(Optional\)	Click the Image omitted: icon-plus.png Plus icon. icon to add an external system. For more information, see <a href="../connecthub-create-external-systems/">Create external systems</a>.<strong>Note:</strong> If you already have an existing system, you can use that system for the MCP connector.</td></tr><tr><td> Connection name	Select New connection and enter a name to uniquely identify the connection. For example, Figma Connection.

|Field|Description|
|-----|-----------|
|Endpoint name|This field is auto-populated with the Connection name.|
|Endpoint URL|Connection URL for the MCP server.|
|Authentication Method|Select **API key**.|
|API key|Enter the API key of the third-party application.|

Click Save.

You are redirected to the third-party page requesting authorization for the MCP client.
Click Approve.

The MCP client for your application is created and appears in the Model Context Protocol list.

Create an MCP Connector with Basic Authentication

Create an MCP Connector with Basic Authentication for connecting to external systems or applications that support MCP.

Before you begin

Role required: sn_mcp_client.admin

About this task

Use Basic Authentication when your MCP server requires a username and password for access. Ensure that valid server credentials are available before configuring the connector.

Procedure

Navigate to All > Workflow Data Fabric > Connect Hub.
Click Create and select Model Context Protocol.

The list of all available MCP connectors is displayed.

Image omitted: custom-connector.jpg
3. Click **Create a custom connector**.

On the form, fill in the fields.

Field	Description
Server name	Name of the MCP server. For example, Figma MCP server.
System	Search for the external system you want to integrate.
Add system \(Optional\)	Click the Image omitted: icon-plus.png Plus icon. icon to add an external system. For more information, see <a href="../connecthub-create-external-systems/">Create external systems</a>.<strong>Note:</strong> If you already have an existing system, you can use that system for the MCP connector.</td></tr><tr><td> Connection name	Select New connection and enter a name to uniquely identify the connection. For example, Figma Connection.

|Field|Description|
|-----|-----------|
|Endpoint name|This field is auto-populated with the Connection name.|
|Endpoint URL|Connection URL for the MCP server.|
|Authentication Method|Select **Basic Authentication**.|
|User name|User name of the MCP server.|
|Password|Password of the MCP server.|

Click Save.

You are redirected to the third-party page requesting authorization for the MCP client.
Click Approve.

The MCP client for your application is created and appears in the Model Context Protocol list.