Create a new MCP data source connection to enable access to external MCP servers and their tools.
About this task
The data source configuration form contains fields that must be completed in order. Fields are organized into logical sections for ease of use. Some fields are always required, while some appear only based on your selections.
Important: Required fields must be filled in. Optional fields can be left empty. Authentication fields depend on the selected authentication type, and certificate fields depend on CA Certificate being enabled.
Procedure
-
From the Data Sources page, click the Create a connection card (displays a "+" icon).
The configuration form opens.
-
In the Name field, enter a descriptive name for your data source.
Use descriptive names that indicate the server's purpose. Examples: "FTM Server", "Data Analysis Server".
-
In the Description field, add a clear description of its purpose.
Explain what data or services this connection provides. Include any relevant context for other users.
- Optional:
To add tags, enter keywords in the Tags field and click Add.
Tags help organize and filter multiple data sources. Example tags: "fraud, payments, security". Tags are useful for managing multiple data sources and can be used for filtering and search operations.
-
From the Transport Type dropdown, select the appropriate protocol based on your server's capabilities.
- Streamable HTTP - For most real-time streaming connections (recommended for most MCP server connections)
- SSE - For server-sent events (ideal for real-time updates and event-driven architectures)
- Proxied - When connecting through a proxy (use when direct connection is not possible)
- REST HTTP - For traditional REST API connections (standard request-response pattern)
-
In the Server URL field, enter the complete endpoint URL.
The URL must include the protocol (http:// or https://) and the full path to the MCP endpoint. Example: https://example.com/mcp
Verify the URL is correct before proceeding.
-
From the Authentication Type dropdown, select the authentication method based on your server requirements.
| Authentication type | Additional fields and actions |
|---|
| None |
No additional authentication fields appear. Use only for internal or trusted networks. Proceed to the next step. |
| Basic |
Enter your account username in the Username field. Enter your account password in the Password field. Password is hidden by default for security. Click the eye icon to toggle visibility if needed. |
| Bearer Token |
Enter your authentication token in the Bearer Token field. The token will be securely stored in the system. Click the eye icon to toggle visibility. Obtain the token from your MCP server administrator. |
| Custom Headers |
Enter the header name in the Header Key field; for example, "Authorization". Enter the header value in the Header Value field. Click the eye icon to toggle visibility. Click Add Header to add additional headers. Multiple headers can be added for complex authentication schemes. |
- Optional:
To configure a custom Certificate Authority certificate, enable the CA Certificate option.
This is required for self-signed certificates or certificates from non-standard CAs.
-
From the Certificate Input Method dropdown, select Text Paste.
-
In the Certificate Content field, paste the entire certificate content in PEM format.
The certificate must include BEGIN and END markers. Example format:
-----BEGIN CERTIFICATE-----
[certificate content]
-----END CERTIFICATE-----
-
Review all entered information for accuracy.
-
Click Add Server to save and establish the connection.
Click Cancel to discard changes.
The system saves the configuration and attempts to connect to the MCP server.
Results
The new data source appears on the Data Sources page with its connection status.
What to do next
After creating the data source, verify the connection:
- Check the connection status indicator on the data source card.
- If the status shows Connected (green dot), the connection is successful.
- If the status shows Disconnected (yellow triangle), verify:
- Server URL is correct and accessible
- Authentication credentials are valid
- Network connectivity is available
- Firewall rules allow the connection
- CA certificate is correct (if used)