What was announced
The release, datelined London on 7 October 2026, says contractors using ProcurePro can ask questions such as "Where are we losing money, and why?" in Microsoft Copilot or Claude. Answers come from their own live commercial data through the new MCP connectors. The company's examples include asking which trades are trending over budget across every live project and what is driving it.
The release does not name a specific Copilot experience, Claude plan, supported region, price or setup procedure. Treat anything beyond "Copilot and Claude via MCP" as unconfirmed.
What MCP is and why it matters here
ProcurePro describes MCP as a shared standard that lets AI assistants connect to software and read real-time data. Instead of building a custom integration for each assistant, the software vendor builds one MCP server and any MCP-capable assistant can use it.
Microsoft documents its own framework along the same lines. Microsoft 365 Copilot supports "federated" Copilot connectors. Per Microsoft Learn, these use MCP to fetch data in real time, use the user's identity and permissions, and don't index external data into Microsoft 365.
Microsoft's page does not list ProcurePro. Its gallery covers partner connectors that Microsoft has approved and published, and nothing in the announcement says ProcurePro has that status. Microsoft's admin controls, such as tenant-level enablement and staged rollout to Entra ID groups, are therefore not confirmed for this connector. Ask ProcurePro and Microsoft how the connector reaches Copilot before assuming any of them apply.
What ProcurePro says about the connector's controls
A ProcurePro blog post dated 28 September 2026 gives more operational detail than the press release. These are vendor statements and have not been independently validated:
- Read-only by design. It can retrieve and report, but cannot award a package, approve a variation, change a contract sum or delete a record.
- Existing permissions. Users sign in with their own ProcurePro account, so project access and role limits carry over. Revoking someone's access also cuts off their assistant.
- Administrator-enabled. An administrator switches the connector on for the business.
- Assistant support. The September post names Claude, Microsoft Copilot and ChatGPT, with Gemini "to follow". The October release mentions only Copilot and Claude, so do not assume ChatGPT or Gemini support from this announcement.
The read-only claim matters in a Microsoft context. Microsoft says write, update and delete actions for federated connectors began rolling out in early October 2026. Where a connector supplies such tools, approval is required by default. If ProcurePro's claim holds, Copilot can answer questions about commercial records but cannot change them.
Where "live data" has limits
ProcurePro's own post concedes the main caveat: an MCP server can only read what is already in the system. If bids, contracts and budgets sit in spreadsheets, shared drives and inboxes, the assistant has no complete record to draw on. Even when the data is in ProcurePro, the answers are only as complete and consistent as what was entered.
The release also says general AI tools "guess and hallucinate" without live data. Connecting a real data source reduces one cause of invented answers. It does not make an LLM's summary or ranking correct, so figures should be checked against the source records before they drive a contract award.
Figures to treat with caution
The release cites two statistics:
- Contractor margins. It says the UK's 100 largest contractors averaged around 3% pre-tax margin and a quarter made less than 2%, attributed to TCI Top 100 2026 and Company Watch.
- Over-budget subcontracts. It says ProcurePro platform data shows one in four subcontracts is procured over budget.
No methodology or underlying dataset is supplied, and the second figure comes from the vendor's own platform. The company boilerplate also claims more than 7,000 projects and over US$120 billion in construction value, which is a corporate claim. The September blog gives different totals (6,000+ projects, over $150 billion), so these numbers are not consistent across ProcurePro's own materials.
Nothing provided shows that the connector improves margins or prevents losses. CEO Alastair Blenkin's framing of a move from "rear-view mirror" to proactive management is a vendor opinion.
Checks for IT and commercial teams
These are prudent steps, not procedures ProcurePro has documented:
- Confirm the supported Copilot path. Ask whether it works in Copilot Chat, Copilot Studio agents or another experience, and which licences it needs.
- Check tenant governance. In Microsoft 365 admin, review whether partner connectors are allowed, and consider staged rollout to a pilot group.
- Confirm identity and scope. Verify that queries run as the signed-in user and what records and tools the connector exposes.
- Ask about retention. ProcurePro's own checklist asks where data goes and whether it is retained for model training. The available material does not answer this for either Copilot or Claude, so get it in writing.
- Validate outputs. Spot-check AI answers against ProcurePro reports before relying on them for commercial decisions.
The bottom line
This is a modest but real example of MCP spreading from developer tooling into line-of-business software that Copilot users already work with. The concrete news is that a construction procurement platform now offers an MCP connector for Copilot and Claude. The performance and margin claims rest on the vendor's word, and the Copilot specifics remain unpublished.