iManage MCP Server uses the Model Context Protocol (MCP) to allow MCP-enabled clients to securely connect to and interface with iManage applications to retrieve information that users may want or perform the tasks they request. For more information about MCP, go to https://modelcontextprotocol.io/docs/getting-started/intro.

This integration facilitates seamless interaction with iManage applications and extends the functionality of MCP-enabled clients while letting you choose how much access to allow to your iManage data. You get the best of both worlds—security and privacy of your data, plus ease of use:

  • All existing iManage security policies, permissions, and audit trails are maintained. You can access only the content for which you have permissions.

  • Data remains in iManage. iManage MCP Server simply provides a secure bridge for MCP-enabled clients to access it.

  • MCP-enabled clients get access to only the user-permitted (authorized) activities and components in iManage applications. You can choose the iManage MCP connector(s) you want to use for each MCP-enabled client and session and also turn off and turn on only as many tools as needed for each connector.

  • Integration of specialized AI solutions/platforms with iManage applications lets you benefit from the best of innovations in the industry while maintaining the security, governance, and content integrity that the iManage platform offers.

NOTE: iManage MCP Server respects iManage Security Policy Manager (SPM) policies. Each request runs as the signed-in user, and SPM restrictions, such as need-to-know restrictions and information barriers, apply at the time of the request. If you can’t see a document in iManage, MCP-enabled clients can’t retrieve it for you through iManage MCP Server.

For more information about iManage Security Policy Manager, refer to iManage Security Policy Manager Administration Guide.