Skip to content

Suggested searches

    Search all documentation ↑↓ to navigate Enter to open Esc to close

    Dust Configuration

    Connect the Probo MCP server to Dust as a remote MCP tool using interactive OAuth with Client ID Metadata Documents, then add it to your agents.

    Markdown

    This guide explains how to connect the Probo MCP Server to Dust, so that your Dust agents can work with your compliance data.

    Dust connects to Probo with interactive OAuth. Probo supports Client ID Metadata Documents (CIMD), so Dust identifies itself with its own metadata URL — no OAuth app, client ID, client secret, or token to manage.

    • A Dust workspace where you are an admin
    • A Probo account with access to the organizations your agents will use

    Choose the endpoint for your Probo environment:

    EnvironmentMCP URL
    Probo UShttps://us.probo.com/api/mcp/v1
    Probo EUhttps://eu.probo.com/api/mcp/v1
    Customhttps://your-probo-instance.com/api/mcp/v1

    The /v1 segment is required.

    1. Log into Dust
    2. Go to Spaces → Tools
    3. Click Add Tool, then Add MCP Server
    4. Enter your Probo MCP URL:
    https://your-probo-instance.com/api/mcp/v1
    1. Choose the Automatic authentication method
    2. Click Connect

    Dust discovers Probo’s authorization server and opens a window to your Probo instance. Log in if prompted, review the requested scopes, then click “Authorize”.

    Once authorized, you’ll be redirected back to Dust and the Probo tools are synced.

    Open the agent you want to use, add the Probo tool from its space, and save the agent.

    Start a conversation with the agent and ask:

    "List all organizations I have access to"

    The agent should use the listOrganizations tool and return your organizations. If it does, the connection is working.

    Self-hosted Probo instances accept only explicitly allowed CIMD clients. Add Dust’s client metadata URL to PROBOD_OAUTH2_SERVER_CIMD_ALLOWED_CLIENT_IDS before connecting. If it is not allowed, the authorization step fails with an unknown client error.

    Need help with the Dust integration?