Start with the task you want to connect
A useful connection should solve a particular problem. Choose the question that sounds familiar:
| Your task | What to look for | What still needs checking |
|---|---|---|
| Find a contract or clause | Document or contract-system search | Search scope, document versions, confidentiality controls |
| Research a case | A legal research connector | Jurisdiction, coverage, citations and current-law verification |
| Review matter documents | A document-management or discovery connector | Matter access, privileged material and user permissions |
| Track a contract obligation | Contract record access or workflow action | Whether the connection reads, edits or triggers a new action |
| Prepare a business transaction review | Data-room or company-document connection | Deal-room restrictions and approved user access |
This directory is a guide to documented connections, not a list of systems that are automatically compatible with your organization.
Connections worth examining
The Claude legal connector marketplace lists legal and document-workflow products. The following examples are shown as vendor-documented discovery starting points, not independent performance assessments.
| AI environment | Documented connection | Typical question to investigate | Official reference |
|---|---|---|---|
| Claude | CourtListener | Can the user retrieve relevant court materials with source references? | Claude marketplace |
| Claude | Ironclad Contracts | What contract information is available to an authorized user? | Claude marketplace |
| Claude | iManage Work | Which document workspaces and versions can be searched? | Claude marketplace |
| Claude | Docusign | Which contract or signature workflows are supported? | Claude marketplace |
| Claude | CoCounsel Legal | How are research functions accessed and checked? | Claude marketplace |
Availability note: Individual products, permissions, supported actions and setup methods may change. A marketplace listing alone does not demonstrate that a connection is enabled for a particular account.
What does a connection actually allow?
An integration can help an assistant find information, read a document, prepare a suggested change or perform an action. These are materially different capabilities.
Reading information can include searching approved workspaces and returning a cited passage. Taking action may include updating a record, creating a document, or starting a workflow. Before allowing an action, identify who authorizes it, what information is recorded, and whether it can be reversed.
Anthropic explains that its connectors work within the permissions available in the source service and that organizations may impose additional restrictions. Its connector guidance is the appropriate starting point for Claude-specific access questions.
Five checks before connecting legal systems
- Confirm the source. Find the current vendor page for the exact connection, not only an announcement about future plans.
- Confirm the identity. Determine whose account and permissions the connection uses. Ask whether shared credentials are involved.
- Confirm data access. List the repositories, matters, client information and metadata the connection may read.
- Confirm permitted actions. Separate read-only use from creating, altering or sending information. Require human approval for consequential steps.
- Run a limited test. Use approved non-sensitive records, check outputs against the source system and keep an issue log.
The testing process should also cover revoked access, incorrect permissions, conflicting document versions and a connection becoming unavailable.
Compare a connection by evidence, not by headline
A useful directory entry should answer: Who publishes it? Which two products does it connect? What task does it support? Is the evidence an official product listing, setup guide or independent test? What permissions are required? When was it last checked?
Where any answer is unknown, it should be shown as unknown—not silently treated as safe or supported. A product may provide a promising demonstration yet still be unsuitable for a confidential matter or an organization's document controls.
Source notes and independence
This page draws on Anthropic's legal marketplace, its legal connector repository, and its help documentation. These are vendor-authored descriptions; they do not independently establish reliability, security or suitability for a particular practice. The directory does not imply an affiliation with any named vendor.
Frequently asked questions
Can I connect my legal AI assistant to the document system we already use? Possibly. Begin with the exact pair of products and check the vendor's supported connection, your organization's configuration and your account permissions.
Will a connected assistant see every client document? It should not be assumed either way. Access depends on the source system, authentication method and organizational controls. Verify it before using client information.
Does a connector make AI-generated legal advice accurate? No. A connection may improve access to relevant materials, but a qualified reviewer must still check sources, reasoning and current law.
Is a plugin the same as an integration? Not always. A plugin may provide instructions or a task workflow; a connector typically provides a way to access another system. Some offerings combine both.
Choose your next step
Browse the documented connections by legal task, then read the vendor's setup guidance and test the specific permission scope. If your first question is whether an AI tool's output can be trusted, continue to the related Legal AI Testing and Data Tools guide (B02-002).
Find your next useful step
Start with the sources and practical checks above, then continue to a related guide.
Browse Tool Connections