Open Claude and for details about adding a custom connector, refer to https://modelcontextprotocol.io/docs/develop/connect-remote-servers.
NOTES:
To add custom MCP connectors, you need a paid subscription to Claude.
Exact details about adding custom connectors aren’t provided here as the UI and the steps may differ depending on various factors including your subscription and account type and whether you're on Windows or macOS.
For the latest information, always refer to the Claude documentation.
As needed, provide the following details to add the iManage connector.
Name: <Name of the iManage connector>
URL: Add the URL of any of the MCP connectors (iManage Work, iManage MCP Search, and iManage Insight+):
NOTE:
If your company uses a custom subdomain, add it and use a dot (.) between the custom subdomain and the domain (cloudimanage) for all three URLs.
Example:
If your custom subdomain is ajubalaw, the URL to add the iManage Work connector would be https://ajubalaw.cloudimanage.com/mcp/work.For an overview of the available connectors, refer to Adding iManage connectors for MCP-enabled clients.
If prompted, provide your iManage credentials and sign in.
Currently, only read permissions are available and selected by default. To allow Claude to connect to iManage with those permissions, select Authorize.
A message is displayed informing you that the iManage Tracker is connected and available in the list of connectors. All available tools for the iManage Tracker connector are also added and enabled by default.
CAUTION: Depending on the permissions check boxes selected while authorizing, some or all tools may be available for your MCP-enabled client.
For more information about all the iManage connector tools that are available when you grant all permissions (by selecting the Allow All check box), refer to Tools available for each MCP connector.
Repeat the above steps for each iManage connector you want to add.