OIA Advisory: iManage MCP and the Evolving AI Ecosystem
Over the last several months, significant developments have emerged across Microsoft Copilot, ChatGPT, Claude and other AI platforms regarding how governed enterprise knowledge can be accessed and used within AI-assisted workflows.
While the terminology continues to evolve, the underlying direction is becoming clearer: Model Context Protocol (MCP) is increasingly emerging as the standard mechanism for connecting AI platforms to governed enterprise systems such as iManage Work. The result is a growing set of options for organisations seeking to leverage their iManage knowledge within AI experiences while maintaining existing security, ethical walls, permissions and governance controls.
New: Microsoft Copilot Sources / Federated Copilot Connectors ("Plug-in")
The most significant recent Microsoft development is the appearance of iManage Work as a Source within Microsoft Copilot through Microsoft's Federated Copilot Connector framework. Microsoft currently lists iManage Work as a preview connector allowing users to search documents, matters, folders and recent activity directly from Copilot.
From iManage's perspective, this is expected to become an increasingly important integration path. As noted during recent discussions, customers ultimately want iManage knowledge to be available wherever Copilot is being used, rather than requiring separate agents, connectors or workflows to be explicitly selected. When fully realised, this model has the potential to expose governed iManage knowledge across Copilot Chat, Word, Excel, PowerPoint, Outlook and other Microsoft experiences.
Importantly:
This is not a separate iManage product.
The Source experience is another way of consuming the underlying iManage MCP Server.
Content remains governed within iManage rather than being broadly replicated into Microsoft's search index.
The capability remains relatively new and continues to evolve rapidly.
Current implementations appear primarily focused on search and retrieval scenarios, with write-back capabilities not currently exposed through the Source model.
At this stage, customers should view Copilot Sources / Plug-ins as strategically significant and highly promising, while recognising that the platform, use cases and operational guidance continue to mature.
iManage Plug-in for Microsoft Copilot Cowork
iManage has also released an official plug-in for Microsoft Copilot Cowork, enabling Copilot to work across governed iManage knowledge alongside Outlook, Teams, SharePoint and other Microsoft 365 data sources.
The significance here is Microsoft's broader vision of multi-step AI-assisted work. Rather than simply retrieving information, Cowork can orchestrate activities across multiple systems and sources within a single workflow.
Like the new Copilot Source experience, the Cowork integration is powered by the iManage MCP Server and reflects Microsoft's movement toward MCP-native integrations rather than traditional point-to-point connectors.
Copilot Studio and Foundry Agents Remain Relevant
The emergence of Copilot Sources should not be viewed as invalidating MCP, Copilot Studio, Foundry Agents or agent-based strategies.
In fact, both Microsoft and iManage continue to position MCP as the underlying integration layer, with Sources, plug-ins and agents simply representing different ways of consuming the same governed knowledge platform.
Whilst Sources may become the preferred experience for general access to knowledge, agents continue to provide capabilities that remain valuable in enterprise scenarios, including:
Department-specific behaviours and instructions
Structured workflows
Governance and auditing controls
Workflow orchestration
Business-specific automation
Future write-back and action-based scenarios
As a result, Sources and Agents should currently be viewed as complementary rather than competing approaches.
MCP Plug-ins Across Chat GPT, Claude and Other AI Platforms
The broader industry trend is arguably even more important.
Recent announcements include an official iManage plug-in for ChatGPT Enterprise / Work, allowing governed access to iManage content directly within ChatGPT. iManage has also previously released guidance for Claude integrations, with both platforms leveraging MCP as the underlying access mechanism.
The strategic significance is that:
Microsoft Copilot
Microsoft Copilot Cowork
ChatGPT Enterprise / Work
Claude for Work
Claude Cowork
are all increasingly converging on MCP as the preferred method for accessing governed enterprise knowledge.
For customers, this reduces long-term dependence on any single AI platform and positions the iManage MCP Server as a common knowledge layer across multiple AI ecosystems.
In practical terms, investments made today in understand, validating and becoming comfortable with iManage MCP, governance and information architecture are likely to remain relevant regardless of which AI platform gains prominence over time.
iManage AI Connector (Preview) – Power Platform and Workflows
Separate from MCP and the newer Copilot Source model, Microsoft also provides the iManage AI Connector (Preview).
This connector focuses on exposing capabilities from iManage's own AI services, including Ask iManage, into Microsoft technologies such as Power Platform and Copilot Studio.
Unlike MCP-based integrations, which expose governed content, actions and workflows directly, the iManage AI Connector is primarily designed to leverage iManage's native AI reasoning, search and contextual understanding capabilities.
While currently less central to most MCP-focused customer conversations, it represents a complementary part of the broader ecosystem and may become increasingly relevant as iManage expands its own AI capabilities.
TL;DR: iManage, MCP and the Evolving AI Ecosystem
The AI integration landscape around iManage is changing rapidly, but the underlying direction is becoming clearer.MCP (Model Context Protocol) remains the core technology behind iManage's AI strategy and is increasingly emerging as the standard method for connecting governed enterprise knowledge to AI platforms.Microsoft Copilot Sources ("plug-ins") are an important new development, providing direct access to iManage knowledge from Copilot and, over time, potentially across Word, Excel, Outlook, PowerPoint and other Microsoft experiences.
iManage believes this may become the most significant Copilot integration model moving forward.The Copilot Source is not a replacement for MCP or agents. It is simply another way of consuming the same iManage MCP Server.Copilot Studio and Foundry agents remain highly relevant, particularly where organisations need workflow automation, governance, instructions, department-specific behaviour, orchestration or future write-back capabilities.
ChatGPT Enterprise, Claude and Microsoft Copilot are increasingly converging on MCP as the preferred way of accessing governed enterprise knowledge. This reduces dependence on any single AI platform and positions iManage MCP Server as a common knowledge layer across multiple AI ecosystems.The newest ChatGPT Enterprise / Work plug-in for iManage is a significant milestone, further reinforcing MCP as the primary integration approach across major AI vendors.
The ecosystem is still maturing. Microsoft Copilot Sources remain relatively new, official guidance is still evolving, and current implementations are primarily focused on search and retrieval use cases.
