MyCase's Claude Connector: What to Check Before Approving New Actions

AI-generated editorial illustration by Viaclause. People and setting are fictional; this does not depict an 8am demonstration or customer.

Before approving MyCase's new Claude connector, ask the vendor to show which operations can read records and which can change them. The distinction matters because the connector's published terms describe its current tools as read-only while also setting out conditions for possible future write tools.

Use the AI contract review evaluation guide to define the buying task and acceptance checks for the wider workflow.

The immediate buyer question is whether a law firm can approve a narrowly defined use today and reliably recognize a later expansion. A feature announcement alone does not settle that operating decision.

What was announced, and what the terms say

Reporting from 8am's September 23, 2026 conference, Bob Ambrogi described the MyCase MCP connector for Claude, including information retrieval, summaries and reporting. His report also distinguishes other announced AI products and their planned availability. We have not tested the connector or independently measured its performance.

8am's terms, Part III, section 8, call the connector an experimental beta. Section 8.D says its tools are currently read-only. It describes possible future writes and says the activity log would identify the action and affected record, without capturing the record's previous contents; such records would not be versioned or restorable through the services. Sections 8.B and 8.E require an eligible Claude Team or Enterprise subscription with training disabled and verification of output before client-matter use. These are published conditions, not evidence that write tools are live.

That creates a concrete procurement task: record the approved capability boundary separately from the product name. A pilot called “MyCase with Claude” is too vague if the capabilities available under that name later change.

Use a capability change record

This is our proposed pilot record. It is not a claim that the product lacks a control, nor a report of a test we performed. Ask the vendor or administrator to demonstrate each answer in an authorized test environment containing synthetic records.

• Operation: the exact tool name or visible action, its version or observation date, and whether it reads or changes information.
• Scope: the test account, permitted matters and data fields needed for the task. Record excluded matters separately.
• Output: where retrieved information appears, what evidence supports a summary, and who checks it before use.
• Approval: who authorizes this operation, whether approval repeats, and what event requires a new review.
• Change handling: how the firm learns that tools, permissions or service terms have changed. Name a person who rechecks the record.
• Recovery: for any future write operation, the before-state evidence, correction method, responsible owner and limits of restoration.

Keep this record alongside the purchase approval. Use an explicit label such as “approved for the observed read-only operations on the synthetic pilot dataset.” Do not describe an untested future capability as already approved.

Separate three things that can look like one task

Hypothetical example: an administrator asks an assistant to “prepare tomorrow's case list.” That could mean reading calendar entries, drafting a proposed list outside the practice-management system, or modifying the system's underlying records. Give those three activities separate lines in the pilot plan.

For the reading step, select a small synthetic dataset with a known answer: two open matters, one closed matter and one intentionally missing date. Ask for the list and compare the answer with the source records. The missing date should remain visibly unresolved rather than becoming an invented deadline.

For a proposed draft, check whether the output is clearly labelled as a draft and whether its reviewer can trace every matter and date to evidence. A polished paragraph is not a substitute for that comparison.

If a write operation later becomes available, make it a separate test. Before running it, agree what can change, how the exact proposed change is shown, and how the authorized reviewer confirms it. Use disposable synthetic records. Record the before and after states and attempt the agreed correction procedure. Do not call an activity log a backup unless the restoration has actually been demonstrated.

A failed or unavailable step belongs in the result as a limitation. It should not be softened into “works with supervision.” Specify what supervision would require and whether the person supervising has the evidence needed to do it.

What should trigger a second review?

Our recommended triggers are a newly available write operation, a broader data scope, a new destination for output, a change in subscription or training settings, or a different person using the connection. The firm can adapt that list to its obligations and approved use. The purpose is to make a change visible before it becomes routine.

The access-revocation test addresses a separate question: whether access stops when permissions are removed. Add it to the pilot, but do not treat a successful revocation check as proof that a record-changing workflow is recoverable.

For outputs that discuss contract obligations, use the evidence-checking prompt to demand exact supporting passages and missing information. A firm's responsible lawyer still needs to determine what may be used in a client matter. The useful purchasing outcome is a documented, bounded task that can be checked, with a clear route for reviewing the next capability change.

Sources

• 8am Terms of Service, Part III, section 8, especially 8.B, 8.D and 8.E, checked September 27, 2026. Primary evidence for current read-only status and stated conditions for possible future write tools. Does not establish product performance.
• At Its User Conference in Las Vegas, 8am Announces MCP Integration and New AI Tools for MyCase, Bob Ambrogi, LawSites, September 23, 2026. Conference reporting and announcement context. The reporter discloses that his son works on 8am AI products.

By Anirudh Menon, Viaclause editor. Sources checked September 27, 2026. The pilot record and scenario are proposed methods, not a product test or legal review.