Dust is now a remote MCP server

🎯 What is it?

Dust can now be connected to any MCP-capable client as a remote MCP server. This means you can access your Dust building blocks—workspace knowledge, Pods, conversations, and files—directly from the other tools you already use, without having to open Dust itself.

💡 Why is it useful?

Until now, reusing your Dust knowledge and artifacts in another tool often meant copy/pasting content back and forth or constantly switching between apps. By making Dust available as a remote MCP server, your trusted context travels with you, so the same knowledge and outputs can be tapped into wherever you work.

⚙️ How does it work?

MCP (Model Context Protocol) is a standard way for applications to securely connect to external sources of context. Any client that supports MCP can now authenticate to Dust and pull in your building blocks on demand. Full setup instructions are available in the documentation.

✨ Concrete Use Cases

Here's how you could use it:

• Working in an MCP-capable coding or writing tool: Pull in relevant workspace knowledge or a past conversation directly into your working environment, without leaving the app you're in.

• Reusing existing artifacts: Reference files or Pod content from Dust inside another client, so your team relies on a single, trusted source instead of duplicated copies.

📈 Benefits for you

Less copy/pasting, fewer app switches, and more consistency. Your teams can reuse the same trusted knowledge and artifacts across tools, which saves time and reduces the risk of working from outdated or fragmented information.

🚀 How to access it?

This is available now to everyone—no feature flag required. To get started, follow the connection steps in the documentation.

A note for workspace admins: you stay in control of access. You can disable MCP server access for the entire workspace, and you can restrict which redirect URIs are allowed during client authentication.