Toolsets

Introduction

Toolsets in DIAL are connections with MCP servers that you can use as tools in Quick Apps 2.0.

Main Screen

On the main screen, you can find all publicly-available Toolsets that have either been published by DIAL users or added via a direct modification to DIAL Core's dynamic settings.

Publicly-available toolsets can be accessed via DIAL Core API or DIAL Marketplace by all authorized users and apps.

Refer to Access Control to lean more about Private and Public logical spaces for objects storage in DIAL.

Folders Structure

Objects in the Public space are arranged hierarchically, similar to a file system. In this part of the screen, you can see the hierarchical structure of folders in the Public space.

Element	Description
Root folder	A root public folder. Contains the sub-folders and toolsets. It is visible to all users.
Sub-folders	Toolsets can be placed in a specific sub-folder for logical organization purposes.
Actions	Hover over any folder to view a context menu icon with actions you can perform in relation to the selected folder. - Rename: Use to rename the selected folder. - Move to: Use to select a target location in the hierarchy to move the selected folder. - Manage permissions: Redirects to Folder Storage to manage access to the folder. - Delete: Use to delete the folder with Toolsets inside it.

Toolsets Grid

Click on any folder to display toolsets in the toolsets grid.

Column	Description
ID	Toolset's unique key.
Version	Version of the toolset.
Author	Username or system ID associated with the user who created or last updated this toolset.
Updated time	Timestamp of the last modification of the toolset. Use to track changes.
Actions	Actions you can perform on the selected toolset: - Open in new tab: Opens a new tab with toolset's properties and parameters. - Duplicate: Use to create a copy of the toolset. - Move to another folder: Use to select the target folder in the hierarchy to move the toolset. - Delete: Use to delete the toolset. Alternatively you can use Bulk Actions in the header to remove multiple toolsets.

Export

Use Bulk Actions in the toolbar to download selected toolsets.

This is useful for migrating toolsets between environments, sharing sets of toolsets with another users, or keeping a point-in-time backup.

To export toolsets:

1. Click Bulk Actions button in the toolbar.
2. Select toolsets by checking the boxes in each row. You can also select the version you want to export.
3. Click Export in the bottom to launch the export modal.
4. In the modal window select the export format: Archive or JSON.
5. Click Export to generate export file and start downloading.

Import

Use Import in the toolbar to upload new or update existing toolsets from ZIP archive. This is essential for migrating, restoring, or sharing toolsets assets between DIAL users.

To import toolsets:

1. Click Import in the toolbar to launch the import modal.

2. Drag & Drop your DIAL Admin archive into the files area or click Browse to open a file picker.

   

3. Select a Conflict resolution strategy. It allows you to decide how to handle existing toolsets with the same identifier and version:

   • Skip: Leave existing toolsets untouched, only new ones will be added.
   • Override: Replace toolsets having the same name and version with the imported ones.

4. Use Ignore paths toggle to skip folder structure from the imported files. When enabled, all toolsets will be imported directly into the root folder without recreating the original folder hierarchy.

5. Click Finish to start.

   

Create

On the main screen you can add new toolsets to the public folder.

Follow these steps to add a new toolset:

1. Click + Create to invoke the Create Toolset modal.

   Field	Required	Description
   ID	Yes	A unique identifier of the toolset.
   Display Name	Yes	A user-friendly label shown throughout the Admin UI and in DIAL Core.
   Version	Yes	Semantic identifier (e.g., 1.2.0) of a toolset's version.
   Description	No	A free-text summary describing the toolset (e.g. purpose and data being fetched).
   External Endpoint	Yes	Endpoint DIAL Core will use to communicate with the toolset.

2. Once all required fields are filled click Create. The dialog closes and the new toolset configuration screen is opened. This entry will appear immediately in the listing under the selected folder once created.

   

Configuration Screen

Click any toolset on the main screen to open a screen with information about the selected toolset and its configuration details.

Properties

In the Properties tab, you can preview and modify selected toolset's basic properties.

Field	Description
ID	Unique identifier of the toolset.
Author	Username or system ID associated with the user who created or last updated this toolset.
Creation Time	Timestamp of when the toolset was created.
Updated Time	Date and time when the toolset's configuration was last updated.
Authentication	Current authentication status of the selected toolset: - Logged out: The toolset in not authenticated with the related MCP server. - Logged in (Personal): The toolset is authenticated for your user only. - Logged in (Organization): The toolset is authenticated for all users in your organization.
Folder Storage	Path to the toolset's location in the hierarchy of the public folder.
Display Name	The name of the toolset assigned by the author.
Version	Version of the toolset. Can be selected from the dropdown to display information for different versions.
Description	A free-text summary describing the toolset.
Icon	A logo to visually distinguish the toolset on the UI. Maximum size: 512 MB. Supported types: .jpeg, .jpg, .jpe, .png, .gif, .apng, .webp, .avif, .svg, .svgz, .bmp, .ico. Up to 1 files.
Topics	Tags that you can assign to toolset. Helps to assign categories for better navigation on UI.
Storage folder	The path to the toolset's location in the hierarchy of folders. It allows you to move the toolset between folders.
External Endpoint	The MCP endpoint that a Quick App can call to fetch external data.
Transport	A transport supported by MCP server. The available options are: HTTP or SSE. Default: HTTP. Choose SSE for server-sent events when supported.
Authentication	Authentication settings for the toolset.
Forward per request key	Set this flag to true if you want a per-request key to be forwarded to the toolset endpoint allowing a toolset to access files in the DIAL storage. Note: it is not allowed to create toolsets with authType.API_KEY and forwardPerRequestKey=true.
Max retry attempts	Number of times DIAL Core will retry a failed call (due to timeouts or 5xx errors).

Authentication

If the toolset you have chosen requires authentication at the related MCP server, you will have to sign in before you can use it. For example, if you are using an application that relies on the MCP toolset and authentication is required, you will not be able to access it unless you are logged in. Therefore, make sure you are authenticated with MCP server you are about to use.

Note, that toolset can be published with credentials by other users. In this case, a toolset can be already authenticated for all users in the organization - Logged in (Organization). You can use it or log out and log back in with your personal credentials - Logged in (Personal).

Refer to DIAL Core to learn more about toolset authentication

Step 1: Select and configure the authentication method

DIAL supports several authentication methods for toolsets:

• OAuth: Authenticate via OAuth 2.0 with an external identity provider. If this option is selected, you have to choose With login for a dynamic registration of clients or With login & configuration for a static registration of clients - depending on what method your MCP server supports. For a dynamic option, it is enough to provide an External Endpoint in the toolset properties. For a static, populate the authentication form with correct values provided by the identity provider:
  • Redirect URI: Redirect URI used during sign in flows. After authentication, the MCP Server redirects the User to the provided URI.
  • Client ID: The unique identifier of the client/application requesting access to the resource.
  • Client Secret: A confidential key used by the client to authenticate itself with the authentication server.
  • Scopes Supported: List of supported scopes that define access levels. May be discovered via .well-known endpoints.
  • Default authorization endpoint: URL for performing authorization. Can be discovered via .well-known metadata if provided by the Authorization Server.
  • Default token endpoint: The URL where the client exchanges the authorization code for an access token. Can be discovered via .well-known metadata if provided by the Authorization Server.
  • PKCE method: The method used for Proof Key for Code Exchange (PKCE), usually plain or S256.
• API Key: Authenticate using API key. If this option is selected, you have to provide the API key and header name in the configuration.
• Without authentication: No authentication enforced, endpoint is publicly accessible.

Step 2: Choose personal or organization authentication

Having selected and configured any authentication method, click Save and Log In to authenticate a toolset with the related MCP server. At this step, prior to the actual authentication, you will be prompted to select between Personal and Organization authentication:

• Personal: the toolset will be authenticated for your user only with the authentication state labeled Logged in (Personal).
• Organization: the toolset will be authenticated for all users in your organization with the authentication state labeled Logged in (Organization). Any user will be able to log out and log back in with personal credentials.

Important: at this step, for authentication with API keys, you will be prompted to provide a valid API key value.

Tools Overview

Tools are specific functions supported by a related MCP server that can be used by clients to perform specific actions. On this screen, you can find and manage all tools supported by the related MCP server.

In case your toolset was created based on the MCP container deployed in DIAL, the content of this screen is inherited from the related MCP container.

Use all tools

Enable Use all available tools toggle to automatically include all tools supported by the related MCP server. When enabled, you cannot add or remove tools manually.

Click on any tool to preview its details or try it out.

Manage tools

Disable Use all available tools toggle to enable a manual tools management mode.

1. Disable Use all available tools toggle and click Manage tool button to open the Manage tools modal.
2. The modal displays all tools available to your user. You can preview and enable/disable each tool individually.
3. MCP sever can support other tools that are not available to your user and therefore are not rendered in the list of available tools. If you know their names, you can manually add them. Manually-added tools are labeled accordingly on the Tools Overview screen.
4. Click Confirm to apply changes.
5. On the Tools overview screen, use the filter to see all tools, just auto-detected tools or manually added tools.
6. Hover over any tool to see its details or try it out.

Try tools

Click or hover over any enabled tool to enter the Try out mode.

In the Try out mode, you can test each enabled tool by sending a sample request to the server. When sending a request, you can use the rendered UI form to populate the request input fields or enter JSON view mode to get access to all the fields supported by the input schema.

JSON Editor

Advanced users with technical expertise can work with the toolset properties in a JSON editor view mode.

Use the JSON Editor toggle to switch between the form-based UI and raw JSON view of the toolset’s configuration. It is useful for advanced scenarios of bulk updates, copy/paste between environments, or tweaking settings not exposed on UI.

TIP: You can switch between UI and JSON only if there are no unsaved changes.

Switching to the JSON Editor

1. Navigate to Assets → Toolsets, then select the toolset you want to edit.
2. Click the JSON Editor toggle (top-right). The UI reveals the raw JSON.

Delete

Use the Delete button in the Configuration screen toolbar to permanently remove the selected toolset. To remove several toolsets, use the Bulk Actions option on the main screen.