u/ShiftGood3066

▲ 5 r/LegaltechEurope+2 crossposts

Open-sourced the first MyCase MCP connector for Claude (15 tools, ABA 512 audit logging). What are we missing?

Hey r/legaltech.

Following up on the Clio MCP we shared a few weeks back. Just open-sourced the MyCase equivalent and would love honest feedback from people who actually use MyCase day to day.

The differentiators:

-Append-only audit log , ABA Opinion 512-aligned. Every Claude-to-MyCase call writes timestamp, tool name, parameters, result count, and MyCase user ID. Kept locally never purged by the software.
  - AES-256-GCM encrypted OAuth token storage. Tokens never sit in plaintext, env vars, or shell history.
  - Conservative 30 req/min rate limiter that respects MyCase's Retry-After on 429s.
  - Write scope is deliberately tight: only create-task and log-call. Cases, contacts, documents, calendar, time entries, and billing are all read-only by design. An LLM that can mutate matter records or invoices is a malpractice incident waiting for a trigger.

Install (assumes MyCase Advanced tier, since Open API access is gated there):

npm install -g u/oktopeak/mycase-mcp

Plus 3 env vars in your Claude Desktop config (client ID and secret from MyCase support, plus a local 64-char encryption key). Five minutes if Node and Claude Desktop are already on the machine.

Repo: github.com/oktopeak/mycase-mcp

Demo: youtu.be/jkQ7BUdXztg

What I'd actually like feedback on:

  1. Audit log format. Is what we capture useful for an ethics review or state bar audit, or are we missing fields someone with ABA 512 review experience would want? Considering adding the IP address of the requesting machine and a session ID, but unsure if that adds signal or just noise.

  2. Write scope. We kept it tight (create-task, log-call). Should create-note or log-time-entry be added, or does that cross the line into "AI mutating billables" territory you don't want nywhere near a model?

  3. MyCase IQ comparison. For firms already paying for IQ on Pro or Advanced: what does IQ actually do well that an open MCP path doesn't, and where does it fall short? Trying to write that comparison piece honestly, not as marketing.

  4. What's the most common MyCase integration pain that ISN'T solved by this connector? Document automation templates, multi-user hosted deployments, cross-system (NetDocuments, iManage, Docketwise), or something else? Asking because it tells us what to build next.

Thanks.

reddit.com
u/ShiftGood3066 — 8 days ago
▲ 14 r/salestechniques+1 crossposts

We're a third of the way into 2026 and I want to know how LinkedIn is holding up for everyone as an actual channel.

A few things I'm seeing on my end:

  • Organic reach feels noticeably softer than 12 months ago, even on posts that used to bang
  • DMs land less often (more "Accept" without reply, more silent reads)
  • The feed is heavier on AI-generated/templated content, which I think is training people to scroll past faster
  • Sales Navigator searches surface the same overworked ICP everyone else is hitting

What are you seeing on your end?

  1. Is your organic reach up, flat, or down vs. last year?
  2. Are you still getting inbound from posts, or has it shifted to DMs / outbound / events / referrals?
  3. Anyone closed a real deal from LinkedIn in the last 60 days - what was the path (post → DM, comment → DM, cold connect, etc.)?
  4. What format is actually working for you right now. Text posts, carousels, video, newsletters, polls?
  5. If you've moved budget/time off LinkedIn, where did it go and is it working better?

Thanks!

reddit.com
u/ShiftGood3066 — 15 days ago
▲ 7 r/LegaltechEurope+1 crossposts

Hey r/legaltech.

Wanted to share something we built and ask for honest feedback from the people who'd actually use i

Wee open-sourced a Claude + Clio MCP connector this week. MCP = Model Context Protocol, Anthropic's standard for connecting Claude to data sources. 15 tools across matters, contacts, documents, tasks, calendar, and billing.

Local-only (stdio transport, nothing leaves the lawyer's machine). MIT license, free. The differentiator: it's the only open-source Clio MCP connector with ABA Opinion 512-aligned audit logging built in. Append-only JSONL log of every Claude interaction with Clio data, kept locally.

Three other open-source Clio MCP options exist; none ship with audit logging.

Install:

npx u/oktopeak/clio-mcp 

Plus 3 env vars in your Claude Desktop config. Five minutes if Node and Claude Desktop are already on the machine.

Repo: github.com/oktopeak/clio-mcp

What I'd actually like feedback on:

  1. Is the audit log format useful for an ethics review or state bar audit, or are we missing fields someone with ABA 512 review experience would want?
  2. We kept write scope tight - only create_task and create_note. Conservative enough, or should we add more?
  3. Region handling: built US/EU/CA support via env var. Anyone using Clio outside US who can test EU/CA?
  4. What's the most common Clio integration pain that ISN'T solved by this connector?

Thanks.

u/ShiftGood3066 — 8 days ago