Adding an MCP Server
Extending Dust's toolset beyond the default list of tools is possible by adding extra MCP Servers
Remote MCP Servers and how to add them.
As an administrator, you can add a Remote MCP Server to your workspace. To do so, navigate to Spaces > Tools. Here, you'll find an Add Tool button.
Clicking this Add Tool button will open a list of Dust-built MCP Servers, and an Add MCP Server button
The interface to add an MCP server
Publicly available MCP servers
You can also use any MCP Server available on the internet. Plenty of MCP providers exists out there and are usable out of the box with Dust.
On the click of the Add MCP Server button, you'll only have to enter the MCP server's public URL, and after a quick synchronization, your tool will be created and ready to be added and used by agents.
Authentication
Depending on the nature of the tool to connect in Dust, the authentication flow might be different. Whenever possible, Dust supports OAuth authentication, and is the preferred authentication method.
In most scenarios, the Automatic option will discover all required configurations from the URL provided, trigger an OAuth login flow and finish the configuration automatically. This is the recommended, most secure way to authenticate to MCP servers.
Alternatively, you can use a Bearer token while setting up the connection to the MCP Server. This token will be sent as an Authorization header in the calls made to that server later.
The Static OAuth option is used in scenarios where a custom OAuth app is needed to access the remote tool. Here, the admin will usually need to
- Create the OAuth app on the remote system (GitHub for example)
- Write down the Client ID and Client Secret
- Input them in Dust
Some providers handle authentication themselves, by authenticating the server with one account. This means that using them in Dust will do all the calls with the account authenticated to the server.
One way to circumvent it is to create one server per person, and to add them to some restricted spaces. This way, the authentication for a person will only be usable inside their own restricted space.
Custom MCP servers
You can also create a MCP Server yourself, and plug it directly into Dust. For this, you will need
- To host it in your infrastructure
- assign it a public URL
- secure its access by creating an Oauth app in your cloud provider, or dropping all network traffic except the white-listed Authorization Header contained in the Bearer Token field
Connectivity to the custom MCP server can be tested using the official MCP inspector tool
Updated 7 days ago