Skip to content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

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.

View as 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.

Prerequisites

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

Endpoint

Section titled “Endpoint”

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.

Connect Probo to Dust

Section titled “Connect Probo to Dust”

1. Add the Probo MCP Server

Section titled “1. Add the Probo MCP Server”
  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

2. Authorize via OAuth

Section titled “2. Authorize via OAuth”
  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.

3. Add Probo to an Agent

Section titled “3. Add Probo to an Agent”

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

Verify Connection

Section titled “Verify Connection”

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 deployments

Section titled “Self-hosted deployments”

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.

Support

Section titled “Support”

Need help with the Dust integration?