Aquifer connects to Microsoft 365 Copilot through Copilot Studio and the Model Context Protocol (MCP). Register an Aquifer MCP server as a tool in your Copilot Studio agent, and your team can query Procore, Sage, ArcGIS, and SharePoint data from Microsoft 365 Copilot in Outlook, Teams, Word, and the Copilot chat surface. Requires a Microsoft 365 Copilot license and Copilot Studio access.
Ask Copilot in Teams or Outlook for project status, commitment totals, vendor history, or change-order summaries — and have it answer from your unified Aquifer data. The Copilot Studio agent calls Aquifer's MCP server; Aquifer joins across Procore, Sage, ArcGIS, and SharePoint; Copilot returns the answer in the surface your team is already in.
Generate draft proposals and bids in Word, grounded in vector-indexed content from your Aquifer datastore. Your historical proposals, bids, technical specs, and owner-reporting narratives are queryable through the same MCP server that exposes structured data — one query layer, two kinds of content.
Build Copilot Studio agents that read Aquifer data as part of approval flows, scheduled reports, or notification workflows. Agents can query Aquifer for the data they need before posting to Teams, sending an email, or generating a Word document.
The MCP server runs inside your Aquifer environment. Copilot queries it through the registered tool connection; nothing is replicated to Microsoft's servers beyond the response payloads Copilot needs to answer a user. Standard audit logging on the Aquifer side.
We use a small number of first-party cookies to understand which pages visitors find useful. No advertising, no third parties. Read our privacy notice.
