LABSCO SUMMARY
Requiring the resource parameter is a small protocol detail with real security value.
The resource indicator ties a token to the specific server it was issued for, so a token obtained for Dust cannot be replayed against a different MCP endpoint that trusts the same authorisation server. Few servers enforce it. Combined with the data-handling position — no training, nothing retained by providers — this is a connection built for organisations that have to answer questions about where their data went.
What it is
Dust's endpoint over their agent platform. Their documentation describes capability areas for the first version and states that the exact tools may change, so no fixed list is published.
What you get
The capability areas Dust documents for this version. Because they say the surface will evolve, the honest thing to work against is the live tool list rather than a snapshot.
Requirements
OAuth 2.0 with PKCE, dynamic client registration and a required resource parameter. Dust states customer data is never used to train models and that third-party providers hold nothing.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Using a Dust workspace from another client
Reach the agents and data you already configured in Dust without moving them.
02
Satisfying a data-handling review
No training on customer data, and zero retention at the model providers.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 Bearer (PKCE S256, DCR + CIMD client registration, resource parameter required)
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://dust.tt/mcpRequirements
- OAuth 2.0 Bearer (PKCE S256, DCR + CIMD client registration, resource parameter required)