Mistral is requiring enterprise customers to replace their Google Drive and Microsoft SharePoint Knowledge Connectors with MCP-based alternatives by August 31, when the existing connectors will be shut down and deleted. The company announced the deadline in its Knowledge Connectors documentation but offered few details about how the new retrieval architecture will work. There's no automatic migration, meaning administrators must install the MCP replacements before every user reconnects their Google or Microsoft account, according to the deprecation notice.
The current system lets an administrator select which Google Drive folders or SharePoint sites the organization wants to access, then Mistral processes those files and stores the resulting index in its European data centers. After the index is built—a process that can require anywhere from a few minutes to several hours depending on data volume—users connect their personal accounts, and when they search in Vibe Work, the connector verifies permissions copied from Google Drive or SharePoint so results include only files they're allowed to see. Scheduled synchronizations capture later changes and deletions. This approach allows Mistral to handle retrieval by searching a prebuilt index whenever a user submits a query.
The company defines MCP as a common interface that enables models to call tools and pull data from external services, the same protocol layer reshaping how AI products connect to external APIs across the industry. In June, Mistral added Google Drive and SharePoint to a directory containing more than 60 integrations, but it didn't explain how those two connectors retrieve documents or identify who operates the underlying MCP servers. The company doesn't run the third-party servers behind these connectors, so it can't promise how they'll behave or what they'll do with customer data. The setup can range from live calls to the source API to a server-managed search index, with any combination in between, and that flexibility means the behavior of a given connector depends entirely on its operator. Mistral hasn't said whether the Google Drive and SharePoint MCP servers retrieve files directly from Google and Microsoft, and any caching remains unexplained, leaving customers unsure where retained data would live. The outgoing Google Drive connector follows the sharing rules already attached to each file, including group and domain access, while SharePoint uses Microsoft Entra ID groups, so older groups created only within SharePoint aren't picked up. Mistral hasn't said whether the MCP replacements will follow the same rules, and OAuth can limit a server's access to the connected user, but that doesn't mean search results will be filtered exactly as they were in the outgoing index.
That gap between the governance Mistral once provided and what it's now handing off to third parties reflects a broader pattern in how enterprises are adopting MCP connectors without fully resolving the governance layer. The protocol wasn't designed to enforce the kind of enterprise permission model the outgoing connectors used; the connector's retrieval layer has to do it. Mistral makes no promise that searches will be as fast or return results of the same quality, and the deprecation notice doesn't say whether the August shutdown will trigger automatic deletion of indexed data or how long that process will take. It also leaves administrators unsure whether they should disconnect the old connectors themselves before the deadline. Because the same connectors work in Vibe Code and Mistral's workflow system, teams can use the same approach to expose external data across chat, coding, and automated jobs—a pattern becoming more common as MCP connectors spread from chatbots into production infrastructure. Mistral also recommends checking server output for signs of prompt injection, advice that underscores the still-emerging challenge of securing the space between AI agents and the external services they access. The forced transition effectively shifts responsibility for data retrieval, permissions enforcement, and security from Mistral's controlled environment to a distributed network of third-party operators, without clear answers about performance, compliance, or continuity. Organizations that built workflows around the predictable behavior of Mistral's in-house connectors now face a short window to evaluate whether the MCP alternatives meet their governance standards—or whether they need to find another path entirely.