Knowledge

A knowledge base is a named set of pages, kept up to date from your connected sources, such as Outlook, SharePoint, Google Mail & Drive, Notion and Slack, on a schedule you set or whenever you ask. You define what it covers as topics, and an agent reads your sources and writes the pages, linking each fact to where it came from. People browse it, and agents read it to ground their answers without searching every source.

A team's knowledge is spread across documents, mail and chat: who owns what, what the team is working on, the words it uses. A knowledge base gathers that into a few pages that stay current. A new joiner can find out who to ask, and an agent can answer a question about the team without searching every source. Today it works best for team knowledge, such as a team's people, projects and glossary. The same building block scales to a project or a whole organization, each with its own topics, and service accounts, coming soon, will let these shared knowledge bases run under credentials your organization controls rather than one person's.

• Facts link to their sources. The agent writes only what it can link back to a source, so you can check any line. For example: "The team owns the ingestion pipeline and its on-call rota." with a link to the Notion page it came from.
• Pages follow your sources. Each run rewrites the pages from what your sources hold at that moment, which is what keeps them current. It also means pages are not edited by hand: to change what a page covers, change its topic or its sources.
• A failed topic keeps its last good page. If one topic fails during a run, the others still update.
• Direct 1
  messages are not used as sources.

In the preview you create and run knowledge bases from any client connected to the Mistral MCP server, such as Vibe, by asking in plain language.

1. Connect your sources in Studio connectors.
2. Create a knowledge base. "Create a knowledge base for the platform team, with topics for people, projects and a glossary, from Outlook, SharePoint, Notion and Slack, refreshed every weekday."
3. Run it. "Run the platform team knowledge base." Runs happen in the background; ask for the status at any time.
4. Use it. Ask "What does the platform team knowledge base say about the Q4 roadmap?", or open it from the Knowledge page in Studio.

• Share a knowledge base with people or with the whole workspace, as viewers. They can read it; they cannot change its topics or sources, run it or delete it.
• Only the owner changes the topics and sources, and only the owner can delete it.
• A knowledge base shared with the workspace needs a name no other knowledge base shared there already has.

• Runs use the owner's connector access. Running a knowledge base under a service account — so it no longer depends on one person's access — coming soon.
• Scheduled refreshes run up to once a day. You can also start a refresh yourself at any time, once the previous one has finished.
• Sharing is read-only, and knowledge bases cannot be renamed.
• Supported sources: Notion, Slack, Gmail, Google Drive, Outlook, SharePoint.

Runs use model inference to read your sources and write the pages, so cost grows with how much your sources hold, how many topics you have and how often it runs.

• Connect a client to the Mistral MCP server, where the knowledge base tools are listed.
• Connect your sources in Studio.
• Agentic Search: search over your own documents.