Dust MCP: query the cockpit from Dust
Idun Cockpit connects to Dust as an MCP server: an administrator of your Dust workspace adds it once and gives it to an agent, then everyone asks that agent their questions. To measure the usage of Dust itself, see our article on Dust and the Dust connector.
What you need
Section titled “What you need”- The cockpit’s connection address. It is on your cockpit’s “Connect” page and ends with
/mcp. - An administrator of the Dust workspace.
- Your name and the cockpit’s access password, for each account that connects. On the public demo, the name is optional and there is no password.
1. An administrator adds the cockpit
Section titled “1. An administrator adds the cockpit”-
Add the cockpit’s server
In Dust, open “Spaces”, then “Tools”. Click “Add Tool”, then “Add MCP Server”, and paste the connection address.
-
Choose how each account connects
For authentication, choose “Automatic”: Dust handles the connection itself. Then choose personal credentials (“Personal credentials”): each account signs in with the cockpit’s access password.
-
Give the cockpit to an agent
Create an agent, for example “Cockpit”: in its editor (“Agent Builder”), at the “Tools & Knowledge” step, click “Add Tool” and choose the cockpit.
2. Each account connects
Section titled “2. Each account connects”-
Connect your account
Ask the agent a question. The first time, Dust asks you to connect: click “Connect”.
-
Sign in to the cockpit
The cockpit’s sign-in page opens. Check that it says “app.dust.tt” or “eu.dust.tt”, and continue only if you started the connection yourself. Enter your name and the cockpit’s access password, allow, then click “Retry” in Dust.
What the cockpit can answer
Section titled “What the cockpit can answer”The cockpit answers with what its screens show. It gives the assistant eleven tools and one prompt template. Each answer gives the date of the data and the link to the screen that shows the same thing.
- Find use cases by word, category or risk, and read a use case’s page, full sheet included.
- Give the use case categories.
- Give the figures of the Home, Adoption, Maturity and Value screens.
- Follow over time, week by week, the people who use each tool, and Dust credits when the cockpit measures Dust.
- Give the recommendations, and the use cases each one unlocks.
- Quote the cockpit’s method, section by section.
- Read the interview notes and the audit deliverables: find which deliverable covers a topic, then read it part by part.
- Give the conversations linked to a use case, with their excerpt if your cockpit has opened it. It is closed by default.
- “Prepare a project brief”: the prompt template that gathers, for a project, similar use cases, measured usage, the gain, the recommendations and the interviews.
For example: “We want to launch a meeting-summary agent: how many people already do this, and in which teams?”
Good to know
Section titled “Good to know”- What the cockpit sees. The cockpit records each call from the assistant: the tool, its parameters, the name given to the connection, the assistant’s name and the duration. It does not keep the text of the answer, and it never sees the person’s conversation with Dust.
- The same pages as the screen. The cockpit only answers with what the pages open to readers show: a closed page is closed to Dust too.
- Read only, with at most 30 calls per minute for each connection.
- A connection lasts 90 days at most. It renews itself until then; after that, you connect again.
- Idun can cut a connection, one at a time.
- Where to find it. The demo cockpit, at demo.idun-group.com, already answers. At a client, access opens cockpit by cockpit.
To see what the tool shows on your own tools, book a call.