Claude iManage Work connectorWhat Claude can do in your iManage Work account.
The Claude iManage Work connector exposes 14 tools, every one of them a read tool. 0 write, 0 undocumented: Claude searches, reads and browses your documents and workspaces. Below: what it finds, what it leaves alone, and why iManage's own docs list more.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude iManage Work connector changes for a law firm
Rather than clicking through iManage Work libraries to find a precedent, you ask Claude. It searches full text, names and comments on its own, reads the document it lands on and discusses it with you in the conversation. Per the publisher, documents stay in iManage with no bulk export, and access is permission-bound and auditable.
Find a precedent. You need a non-compete clause already negotiated: search combs document text and workspaces, then download_document pulls the content so Claude can quote the relevant passage.
Pick up a live matter. get_recent_workspaces and get_recent_documents bring back what you opened lately, and get_container_children lays out what a folder holds.
Trace a document's history. get_document_versions shows who changed what and when, version by version, while get_document_profile tells you which client and matter it belongs to.
What Claude does not do with this connector: by default the sheet exposes no tool to create a folder, move, upload or rename a document. iManage's documentation does describe some; the limits section sets the two sources side by side. Nothing runs on its own either: no tool wakes up when a document is filed. For that kind of tracking you need an automation tool, a different job; the Integrations hub covers that side.
The vocabulary in one minute
Five words you will meet while connecting iManage Work.
- Connector
- The link you set up once between Claude and a service, so Claude can work with it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude picks the ones it needs, and the directory sheet lists them all.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use from then on. Granted once, and taken back the same way.
- Directory
- Claude's official catalogue: every connector gets a sheet with its publisher, its purpose and the full list of its tools.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect iManage Work to Claude in three steps
- 01
Find iManage Work in your settings
Open Claude's settings, go to Customize then Connectors, and locate iManage Work in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before you can sign in.
- 02
Start the connection
Hit Connect on its row, then sign in through the window that the service opens on its own side. If the link ever breaks, use Disconnect and connect it again.
- 03
Review the authorization screen
Read the authorization screen before you accept: it belongs to the service, and it sets what the access covers. You can also revoke that access later from your iManage Work account.
The 14 iManage Work read tools
iManage Work gives Claude 14 tools: 14 that read your account, 0 that change something in it.
All 14 tools on the sheet read: search, lookups, profiles, versions. None writes to iManage. Names stay exactly as Claude shows them.
- 14 read
What Claude reads (14)
14 toolsFourteen tools that look through your documents and matters without touching them.
download_document
Pulls the text content of a document by its ID, in its latest version. Claude can then summarize it, compare it with another draft or extract a clause.
fetch
Returns the text of a document identified by its ID, much like the download tool but under a different name. Like the other ID-based tools, it starts from an identifier, not a name.
get_container_children
Lists what a workspace, tab or folder holds: subfolders, documents and tabs. Each call returns at most 500 items, and Claude calls it again to walk through the rest.
get_document_profile
Reports the properties attached to a document, including its client and workspace information. Think of it as the file's identity card rather than its text.
get_document_versions
Brings back a document's full history: version numbers, authors, modification dates, file sizes and comments, up to 1000 versions.
get_libraries
Lists every iManage library you have access to. iManage scopes it to the signed-in user.
get_recent_documents
Returns the documents you accessed recently, the most recently opened first.
get_recent_workspaces
Returns the workspaces, or matters, you opened lately. iManage uses both words for the same thing here.
get_rows_from_csv_document
Reads every row of a CSV document stored in iManage. Claude can then sort, count or summarize that data in the conversation.
get_user_information
Reports information about users of the iManage Work system. With an empty query it describes the signed-in user.
get_workspace_profile
Returns a workspace's profile from its ID: the set of properties describing the matter or the client it gathers together.
get_workspace_templates
Lists the workspace templates in a library, those predefined folder structures that keep legal matter files consistent and organized.
search
Searches iManage Work in plain language across names, descriptions, comments, full document text and workspace names. iManage tells it to run one well-built search per question.
search_workspaces
Finds workspaces matching the criteria provided, for example to learn who owns a given matter. Claude can follow up with that owner's user details.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The 14 tools on the sheet only read, but the rule stays in place.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without confirmation. They can also cap what a connector may do across the organization, keeping reads and shutting writes for instance, and nobody bypasses that from a personal account. On the iManage side, the publisher describes permission-bound, auditable access: Claude only sees what your iManage permissions already open to you.
Which plans it is available on
None of the 819 sheets in the directory shows availability by plan. Connector by connector, that information is not published anywhere: a genuine gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can connect. For the current state, check the iManage Work sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a document is filed or a version is added.
By default the sheet exposes only reads, but that is an observed floor: an admin can open actions that appear on no public sheet, and iManage does document some. The partner badge is not a security audit, and Anthropic says so on every sheet: it does not choose the publisher's tools and does not vouch for their behavior. This connector is documented by its sheet and iManage's help pages alone. To compare with another connector's page, see the Claude agility-cms connector.
Can the iManage Work connector write to iManage?
- Claude directory sheet ↗October 1, 202614 tools listed, all read tools: search, browsing, text download, profiles and versions.
- iManage MCP Server help, tools page ↗undatedThe publisher also describes 7 write tools: creating workspaces, folders and document relations, updating profiles, moving and uploading documents.
What this page followsThe sheet is what Claude exposes as of October 1, 2026: read only. iManage's undated page describes a wider scope that does not show on the sheet, so this page presents no write tool as available. Check the tool list and the directory sheet on your own account.
Need help connecting iManage Work to Claude?
A person reads every message.