Dust MCP server
Secure messaging and collaboration
Dust is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.
- Tools
- 7
- Works with
- Any MCP client
- Auth
- Custom auth
- License
- MIT, open source
- Updated
- September 2026
About the Dust MCP server
Connect Dust once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Dust and 760+ other apps over a single connection, on our cloud or a self-hosted install.
Tools
Dust tools your AI can run
Once connected, your assistant can call any of these Dust actions by asking in plain language.
Create conversation
Create a new conversation with a specific Dust assistant
9 fields
Get existing conversation
Get an existing conversation
2 fields
Reply to conversation
Send reply to existing conversation
6 fields
Add fragment to conversation
Create a new content fragment in a conversation. Content fragments are pieces of information that can be inserted in conversations and are passed as context to assistants to when they generate an answer.
3 fields
Add or update document
Insert a new document to a Data Source (or update an existing one)
6 fields
Upload file
Upload file to be used in conversation
1 field
Custom API Call
Make a custom API call to a specific endpoint
10 fields
Give your assistant Dust
Connect Dust once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.
Dust MCP, answered.
No. That is the point of it. One Activepieces server exposes Dust alongside every other piece you connect, so your client keeps a single connection.