Skip to main content

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

Restricting an MCP server to skills

When configuring an MCP server in Spaces > Tools, enable the Restrict this tool to skills checkbox to make its tools available only through skills that reference them. Restricted tools are hidden from direct selection in the agent builder and input bar, cannot be added directly to conversations or agents, and are excluded from just-in-time tool discovery. To use a restricted tool, add it to a skill: in the skill editor, type / in the instructions and select the tool. See Creating a skill. Agents get the tool when they use that skill. Who can use the tool through a skill depends on the spaces involved:
  • If the tool is in a space that everyone in the workspace can access, such as Company Data, any builder can add it to a skill, and every member can use that skill.
  • If the tool is in a restricted space, or the skill also uses knowledge or tools from other spaces, only people with access to all of those spaces can use the skill.
Restrict this tool to skills controls how a tool is used, not who can use it. To limit who can use a tool, add it to a restricted space.

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. Some examples of publicly available MCP servers:
  • Attio MCP, URL: https://mcp.attio.com/mcp (OAuth). Search, create, and update CRM data in your Attio workspace.
  • Atlassian Rovo MCP, URL: https://mcp.atlassian.com/v1/mcp/authv2 (OAuth). Work with Jira and Confluence. Use this exact URL: with older Atlassian URLs, you can approve access on the Atlassian screen but the connection never completes. Dust also has built-in Jira and Confluence tools.
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.
Connecting with a Bearer token will often link the Dust connection with a single account on the third party service. 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.
The Static OAuth option is used in the most secure 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
The process is slightly different from platform to platform, please refer to the vendor’s documentation

If automatic setup fails

Automatic setup only works if the MCP server lets Dust register itself as an OAuth app. When it doesn’t, Dust shows one of these errors:
  • Failed to register client, this server might require a pre-approval process. The server supports automatic setup but hasn’t approved Dust.
  • This server does not support automatic OAuth setup (no dynamic client registration endpoint). The server doesn’t support automatic setup at all.
The restriction comes from the provider, not from Dust. To connect the server, do one of the following:
  • Use Static OAuth. Create an OAuth app with the provider, or ask them for one, then enter its client ID and client secret in Dust. When you create the app, register the Static OAuth callback URLs listed in Whitelisting Dust as an MCP Provider.
  • Ask the provider to approve Dust. Some providers handle this through their developer or partner program. Share the callback URLs listed in Whitelisting Dust as an MCP Provider with them.

If you approve access but the server never connects

If you approve access on the provider’s screen but the server still isn’t connected in Dust, check whether the provider publishes a newer MCP URL. Add the server again with that URL, then connect. For example, the Atlassian Rovo MCP server needs https://mcp.atlassian.com/v1/mcp/authv2.

Example : Setup the official Github MCP with a Static OAuth connection in Dust

Github’s official documentation explains this process in details here https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app https://github.com/mcp/io.github.github/github-mcp-server Which translates to the following setup process.
  1. In Github : create an OAuth app from the developer settings page
    1. write down the client ID and client Secret
    2. Add the following callback URI to your OAuth app:
  2. In Dust : Navigate to Spaces > Tools > Add tools > Add MCP server and use the following settings
    1. Static Oauth URL : https://api.githubcopilot.com/mcp
    2. OAuth token endpoint : https://github.com/login/oauth/access_token
    3. OAuth Authorization Endpoint : https://github.com/login/oauth/authorize
    4. OAuth scopes : [let your github security admin decide this] but recommendation is “repo, user”
    5. Use custom headers : no
  3. Connect.

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
If your server only accepts traffic from known IP addresses, see Static egress IP addresses. Dust only calls an MCP server from a static IP when the server is on a domain verified for your workspace.
Connectivity to the custom MCP server can be tested using the official MCP inspector tool

Whitelisting Dust as an MCP Provider

If you operate a third-party MCP server and want to support Dust users connecting to it, whitelist the following Dust callback URLs in your OAuth authorization server. This enables the OAuth authentication flow when customers add your server in Dust, and is recommended over Bearer token authentication for a better user experience. It may also be required to get your server listed on the Dust integrations page or in the Dust app. Register all of the following callback URIs for every Dust workspace, including EU workspaces. This includes workspaces that previously registered a region-specific eu.dust.tt callback. OAuth (with Dynamic Client Registration): Static OAuth: