Skip to main content
Unlike local AI tools that run the Transform MCP server through a local bridge, Dust connects directly to the hosted Transform MCP server as a remote MCP server. A Dust workspace admin adds the server once by its URL; builders can then attach the Transform tools to any agent in the Agent Builder.

​
Requirements

Before you begin, you must have the following:
  • A Dust workspace, and the admin role within it. Only admins can add remote MCP servers. Sign in to Dust.
  • To use Bearer token authentication, you will need an Unstructured API key. This method of authentication is best for headless or shared-service setups. Get an API key. This is not required for you to use the recommended Automatic (OAuth) sign-in flow.

​
Add the Transform MCP server

Adding a remote MCP server is an admin action. If you are not a workspace admin, ask one to complete this section.
  1. Sign in to Dust as a workspace admin.
  2. In the sidebar, go to Spaces, and then click Tools.
  3. Click Add Tools, and then click Add MCP Server.
  4. For the server URL, enter the following:
  5. Choose an authentication method:
    • Automatic (recommended): Dust discovers the Transform MCP server’s OAuth configuration from the URL and starts a sign-in flow. Follow the on-screen directions to sign in to Unstructured and approve access.
    • Bearer Token: Paste your Unstructured API key. Dust sends it as an Authorization header on every call to the server. Use this for headless or shared-service setups.
  6. Choose how credentials are shared:
    • Shared: one connection is used for the entire workspace.
    • Personal: each user authenticates individually the first time they use the tool.
  7. Click Connect. Dust synchronizes the Transform tools and makes them available to your workspace.

​
Attach the tools to an agent

After the server is connected, a builder can add its tools to an agent:
  1. In Dust, open the Agent Builder for a new or existing agent.
  2. In the agent’s Tools section, add the Unstructured Transform tools.
  3. Set each tool’s stake (approval level) to match how much oversight you want:
    • request_file_upload_url, check_job_status, get_job_results: low stake (run without approval).
    • start_transform_job: medium or high stake if you want a person to confirm before a partitioning job runs.

​
Partition your source files

Transform MCP partitioning requests have the following limits:
  • Each file must be of a supported file type.
  • Each file must be 50 MB or less in size.
  • Each request must have 10 files or fewer.
  • Only 5 requests can be running at a time.
The Transform MCP server is designed to notify Dust about these limits. Because of this, your Dust agent should notify you whenever it encounters a file that exceeds 50 MB in size. Also, the agent should formulate strategies to send requests that are 10 files or fewer and not cause more than 5 requests to be running at a time.
  1. Start a conversation with an agent that has the Transform tools attached.
  2. Provide the files you want Transform to partition, and ask the following:
The agent drives the Transform job lifecycle for you: it requests an upload URL, uploads each file, starts the transform, polls for status, and returns the results, one output per input file.

​
Troubleshooting

  • Sign-in fails before the Unstructured login screen appears. Your setup may not support automatic OAuth discovery. Remove the server and re-add it using Bearer Token authentication with your Unstructured API key.
  • 401 Unauthorized on tool calls. Re-check your API key (Bearer token), or re-run the OAuth flow (Automatic).
  • Members cannot add the server. Adding a remote MCP server is an admin-only action. Ask a workspace admin to add it; members attach the synced tools to agents afterward.

​
Next steps

​
Questions? Need help?