Claude Can Now Work Inside MyCase. Check the Controls Before You Connect It.

MyCase now exposes 73 actions through Claude. Learn how law firms should govern approvals, audit trails, source links, and reversible changes.

MyCase recently launched a connector that lets law firms work with their practice-management data from inside Claude.

According to LawNext’s report, the connector supports 73 actions across cases, clients, documents, billing, and intake. A user can ask for a case summary, download documents for use in Claude, find outstanding invoices, or build reports and dashboards from MyCase data.

More than 60 firms used the connector during its preliminary release. Most had five or fewer lawyers.

This is already a small-firm issue. The governance question is no longer limited to whether Claude may read a document someone uploads. It now concerns an ongoing connection to the firm’s system of record.

The interface changed, but the data did not

MyCase says the connector gives firms access to their data through the interface they prefer. A lawyer can work in Claude instead of moving through MyCase tabs and reports.

That convenience can hide where the information comes from and what happened to it along the way.

The user still signs in with an identity. MyCase permissions still determine which matters and records the user can reach. The Claude account has its own terms, retention settings, administrators, and security controls. Documents downloaded into Claude may now exist outside the practice-management platform.

The firm needs to understand the complete path:

  • Which MyCase account authorized the connection
  • Which Claude account receives the data
  • Which matters, clients, documents, and financial records are available
  • Which of the 73 actions the user can invoke
  • What activity appears in MyCase, Claude, or another audit log
  • Whether the firm can revoke the connection centrally
  • What copies remain after access is removed

A connector does not create new permissions in MyCase, but it can make existing access faster and easier to use. As we covered in Your AI Assistant Will Inherit Every Bad Permission You Already Have, that includes stale or overly broad access.

Inventory the actions instead of approving the connector as one thing

“Connect Claude to MyCase” sounds like a single decision. Seventy-three available actions make it many decisions.

Reading a matter summary is different from downloading a privileged document into another platform. Finding an unpaid invoice is different from taking an action that affects a client or financial record. A firm may be comfortable with one and unwilling to allow another without approval.

Before enabling the connector broadly, obtain the current action list from MyCase and classify it. At minimum, separate:

  • Read and search actions
  • Document downloads or exports
  • Drafting and analysis using matter data
  • Actions that create or modify a record
  • Client communications
  • Billing, payment, or intake activity

The exact list and capabilities may change as the product develops. That is why the inventory needs an owner and a review date.

If the platform cannot limit individual actions, the firm still needs written rules about what users may do and a monitoring process that can detect exceptions. Access should begin with a small group whose matters and responsibilities fit the pilot.

8am is also developing a native MyCase Firm Agent. LawNext reports that its results are expected to include citation links back to MyCase documents and sources. Results reached through the Claude connector may not include those same links.

That difference affects review.

A summary without source links can sound complete while leaving the lawyer to reconstruct which note, document, time entry, or financial record supported it. If the answer influences a filing, client update, deadline, or billing decision, the reviewer needs a reliable way back to the record.

The connector should not become its own authority. Treat its output as a starting point and confirm material facts in MyCase or the underlying document. Record the source when the answer is used outside a casual internal conversation.

This is the same problem discussed in The Citation Exists. Did Anyone Check the Quote?. A plausible answer and a working connection do not prove that the source supports the final statement.

Decide what belongs outside MyCase

One example in the announcement is downloading MyCase documents into Claude for use with Claude’s other tools. That can be useful, but it crosses a boundary.

The firm should confirm that employees use an approved business or enterprise Claude environment with the required contractual and administrative protections. Consumer accounts should not become an alternate workspace for client files.

The policy should address:

  • Which document types may leave MyCase
  • Whether restricted matters are excluded
  • How ethical walls apply through the connector
  • Whether downloaded files may be retained in Claude projects
  • Who can share outputs or conversations
  • How legal holds and deletion requirements apply

Test with users on both sides of a restricted matter. Search by topic and document type rather than relying on the client name. A permission error is easier to find during a pilot than after the connector becomes part of everyone’s daily routine.

Give the connection an owner and an off switch

Someone at the firm should own this integration. That person does not have to review every prompt, but they should know who has access, which account types are approved, where logs live, and how to disable the connector.

Review access when an employee changes roles or leaves. Recheck the action inventory when MyCase or Anthropic updates the integration. Include the connector in the firm’s vendor register, incident-response plan, and AI policy.

The offboarding test is simple: if the firm disconnects Claude today, can it show that MyCase access ended, identify what data had already been transferred, and determine what remains in Claude?

If nobody can answer those questions, the connection is not yet managed.

Pilot the workflow, not the product

Choose one useful task, such as a morning matter summary or an outstanding-invoice report. Define which records the task may use, who checks the result, what must remain in MyCase, and how the firm will measure whether the connector saved time.

Then review the logs and exceptions before adding another workflow.

MyCase and Claude can remove a lot of tab switching. The firm still owns the permissions, client confidentiality, source verification, and actions taken through the connection.


If your legal applications are adding AI connectors faster than your policies can keep up, Artech can help inventory the access, test the boundaries, and document the approval process.