iManage MCP

Connect iManage Work from Connections to let an agent search and retrieve documents using the permissions of the iManage user who authorizes the connection.

Before You Start

You need an iManage Cloud account and an administrator who can enable iManage MCP Service and permit your user to access it. Ask your administrator which Work MCP endpoint to use and which tools are enabled for your organization.

Your BotDojo deployment must use HTTPS. iManage requires an HTTPS OAuth callback, including for development and testing; an HTTP localhost callback will not work. BotDojo handles client registration and the callback automatically, so you do not need to enter a client ID or secret.

You also need permission to add a Connection in the intended BotDojo project or personal workspace. If iManage is missing from the catalog, ask a BotDojo administrator to allow Remote MCP Connections there.

Connect iManage

1. For a project connection, open Context → Connections → Add Connection. For a personal connection, open Personalization → Connections and select Add beside My Connections.

2. Search for iManage and select it.

3. Review iManage MCP Server URL. The default Work endpoint is:

   https://cloudimanage.com/mcp/work
   

   If your organization uses a custom subdomain, enter the endpoint provided by your administrator:

   https://<subdomain>.cloudimanage.com/mcp/work
   

4. Select Connect, sign in to iManage, and review the requested permissions.

5. Return to BotDojo after authorization. BotDojo checks the connection and discovers the tools exposed by the server.

BotDojo uses the existing Remote MCP OAuth discovery flow. Review the permissions on the vendor consent screen; this catalog entry does not enforce a Work-only OAuth scope.

Use the Work MCP URL, rather than the iManage document-browser URL or sign-in URL.

Choose Document Tools

Open the saved connection and review its Tools before giving an agent access:

1. Refresh the tools if discovery has not completed.
2. Enable only the search and document-retrieval tools required for your workflow.
3. Disable write tools for a document-search workflow. The server's available tools depend on your administrator's configuration and may change.
4. Set Default Approval to Deny so newly discovered tools are not automatically allowed.
5. Save the connection and grant the intended users, agents, or workspace access.

The connection uses the authorizing iManage user's permissions. Sharing it in BotDojo does not sign each recipient into their own iManage account. Limit sharing to the intended audience, and use separate personal connections where each person needs their own iManage identity.

Verify Search and Retrieval

1. Put a non-sensitive test document in a location the authorizing iManage user can access.
2. From an authorized BotDojo workspace, ask the agent to find that document by name.
3. Ask the agent to retrieve and summarize it, identifying the source document.
4. Confirm the answer matches the document and that a document outside the authorizing user's access cannot be retrieved.
5. Reopen the connection and repeat the search. Include a later check after token expiry to verify that access refreshes successfully.

Available search and retrieval tools vary by tenant. Check the discovered tool descriptions rather than assuming a fixed tool list.

Troubleshooting

References

• iManage Work MCP connection setup
• iManage MCP Server administration
• iManage OAuth and HTTPS requirements
• iManage Work connector tools
• BotDojo Connection access and approvals