Add the Version Story connector (commercial-legal, corporate-legal, litigation-legal)

CONNECTORS.md

@@ -29,6 +29,7 @@ Connectors shipped in the default `.mcp.json` of each plugin:
 | **Descrybe** | legal-clinic, ip-legal, law-student |
 | **Definely** | commercial-legal, corporate-legal |
 | **iManage** | commercial-legal, corporate-legal |
+| **Version Story** | commercial-legal, corporate-legal, litigation-legal |
 | **Solve Intelligence** | corporate-legal, ip-legal |
 | **TopCounsel** | commercial-legal, corporate-legal, litigation-legal |
 | **Box** | corporate-legal |

README.md

@@ -310,6 +310,7 @@ These plugins ship connectors for the systems legal teams live in. A connector g
 | **Ironclad** | Read the contract register, renewal dates, clauses | `commercial-legal` | Customer subscription |
 | **DocuSign / DocuSign CLM** | Envelope status, executed contracts, CLM metadata | `commercial-legal` | Customer subscription |
 | **iManage** | Read from the DMS — matter workspaces, document versions | `commercial-legal`, `corporate-legal` | Customer subscription |
+| **Version Story** | Redlines between document versions — Word tracked changes, PDF, merged drafts, version history | `commercial-legal`, `corporate-legal`, `litigation-legal` | Version Story account; OAuth |
 | **Everlaw** | E-discovery productions, tagged sets, chronologies | `litigation-legal` | Customer subscription |
 | **CourtListener** | Federal dockets and opinions | `legal-clinic`, `ip-legal`, `litigation-legal`, `law-student` | Public; optional API key |
 | **Trellis** | State court dockets and motions | `litigation-legal` | Customer subscription |

commercial-legal/.mcp.json

@@ -30,6 +30,12 @@
       "title": "Definely",
       "description": "Live, deterministic access to contract structure — resolve definitions, validate cross-references, map dependencies, run structural diffs."
     },
+    "Version Story": {
+      "type": "http",
+      "url": "https://mcp-compare.versionstory.com/mcp",
+      "title": "Version Story",
+      "description": "Deterministic document comparison — turn any two versions into Word tracked-changes or PDF redlines, merge parallel edits into one draft, build version histories with every change attributed."
+    },
     "Slack": {
       "type": "http",
       "url": "https://mcp.slack.com/mcp",
@@ -47,6 +53,7 @@
     "contract-management",
     "e-signature",
     "legal-document-management",
+    "document-comparison",
     "email",
     "documents",
     "chat",

commercial-legal/CLAUDE.md

@@ -57,6 +57,7 @@ is the final escalation point. We process roughly [N] agreements per month, most
 | CLM (Ironclad, Agiloft, etc.) | [PLACEHOLDER ✓/✗] | Manual record-keeping; renewal-tracker runs against a local register |
 | E-signature (DocuSign, etc.) | [PLACEHOLDER ✓/✗] | User routes for signature outside the plugin |
 | Document storage (Drive / SharePoint / Box) | [PLACEHOLDER ✓/✗] | User uploads agreements directly for each review |
+| Document comparison (Version Story) | [PLACEHOLDER ✓/✗] | Version differences described in prose; no tracked-changes or PDF redline produced |
 | Slack | [PLACEHOLDER ✓/✗] | Alerts and stakeholder summaries delivered inline instead of posted |
 
 *Re-check: `/commercial-legal:cold-start-interview --check-integrations`*

commercial-legal/README.md

@@ -70,13 +70,16 @@ Ships with connectors configured in `.mcp.json`:
 
 - **Ironclad** — contract lifecycle management
 - **DocuSign** — signature status and envelope tracking
+- **Version Story** — document comparison and redlining
 - **Slack** — search messages, read channels, find discussions (general bucket)
 - **Google Drive** — search, read, and fetch documents (general bucket)
 
 With a [CLM] connected: reviews check for prior agreements with the same counterparty, bulk-load the renewal register, create records with review memos attached.
 
 With DocuSign connected: track signature status, route envelopes in approver order.
 
+With Version Story connected: turn any two versions of an agreement into a Word tracked-changes or PDF redline, merge parallel edits into one draft, and trace how a provision evolved across versions.
+
 ## Quick start
 
 ### 1. Get interviewed

commercial-legal/skills/cold-start-interview/SKILL.md

@@ -35,7 +35,7 @@ Runs the cold-start interview. First run writes `~/.claude/plugins/config/claude
 
 ## `--check-integrations`
 
-Re-runs the integration availability check (CLM, e-signature, document storage, Slack) and updates `## Available integrations` in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. Does not re-interview. Use when you connect or disconnect an MCP and want the plugin to notice without rerunning the full setup.
+Re-runs the integration availability check (CLM, e-signature, document storage, document comparison, Slack) and updates `## Available integrations` in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`. Does not re-interview. Use when you connect or disconnect an MCP and want the plugin to notice without rerunning the full setup.
 
 When probing: only report ✓ if an MCP tool call actually succeeded. Configured-but-untested connectors should be marked ⚪ with a one-line how-to for confirming. Never report ✓ based on `.mcp.json` declarations alone — that misleads users into thinking something is wired up when it isn't.
 
@@ -194,7 +194,7 @@ If the answer is 3, add:
 
 #### What's connected?
 
-> This plugin can work with: CLM (Ironclad, Agiloft, etc.), e-signature (DocuSign, etc.), document storage (Google Drive, SharePoint, Box), and Slack. Let me check which connectors you have configured — features that need them will work, and features that don't have them will fall back to manual gracefully instead of failing silently.
+> This plugin can work with: CLM (Ironclad, Agiloft, etc.), e-signature (DocuSign, etc.), document storage (Google Drive, SharePoint, Box), document comparison (Version Story), and Slack. Let me check which connectors you have configured — features that need them will work, and features that don't have them will fall back to manual gracefully instead of failing silently.
 
 **Check what's actually connected, not what's configured.** A connector listed in `.mcp.json` is *available*. A connector that's actually responding is *connected*. These are different, and confusing them destroys trust. For each connector this plugin uses:
 
@@ -432,6 +432,7 @@ contract lifecycle management.
 | CLM (Ironclad, Agiloft, etc.) | [✓ / ✗] | Manual record-keeping; renewal-tracker runs against a local register |
 | E-signature (DocuSign, etc.) | [✓ / ✗] | User routes for signature outside the plugin |
 | Document storage (Drive / SharePoint / Box) | [✓ / ✗] | User uploads agreements directly for each review |
+| Document comparison (Version Story) | [✓ / ✗] | Version differences described in prose; no tracked-changes or PDF redline produced |
 | Slack | [✓ / ✗] | Alerts and stakeholder summaries delivered inline instead of posted |
 
 *Re-check: `/commercial-legal:cold-start-interview --check-integrations`*

corporate-legal/.mcp.json

@@ -41,13 +41,20 @@
       "url": "https://api.solveintelligence.com/mcp/",
       "title": "Solve Intelligence",
       "description": "Patent workflows — search patent and non-patent literature, legal texts, SEP technical standards, prior art, claim analysis."
+    },
+    "Version Story": {
+      "type": "http",
+      "url": "https://mcp-compare.versionstory.com/mcp",
+      "title": "Version Story",
+      "description": "Deterministic document comparison — turn any two versions into Word tracked-changes or PDF redlines, merge parallel edits into one draft, build version histories with every change attributed."
     }
   },
   "recommendedCategories": [
     "legal-document-management",
     "virtual-data-room",
     "contract-review",
     "board-governance",
+    "document-comparison",
     "documents",
     "chat",
     "email"

corporate-legal/CLAUDE.md

@@ -63,6 +63,7 @@ The deliverable should read like a partner wrote it. The meta-commentary goes in
 | VDR (Intralinks, Datasite, Box) | [✓ / ✗] | Diligence pulls from local folder; user drops docs in `~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/vdr-mirror/` |
 | Board portal (Diligent, BoardEffect) | [✓ / ✗] | Minutes/consents work from local templates; no portal posting |
 | Document storage (Google Drive, SharePoint, Box) | [✓ / ✗] | Read local paths; no cross-system search |
+| Document comparison (Version Story) | [✓ / ✗] | Version differences described in prose; no tracked-changes or PDF redline produced |
 | Slack | [✓ / ✗] | Briefs emitted as files only; no in-channel summaries |
 
 *Re-check: `/corporate-legal:cold-start-interview --check-integrations`*

corporate-legal/README.md

@@ -84,6 +84,7 @@ Ships with:
 - **Slack** — search messages, read channels, find discussions (general bucket)
 - **Google Drive** — search, read, and fetch documents (general bucket)
 - **Box** — data room and document management
+- **Version Story** — document comparison and redlining across versions
 
 Intralinks, Datasite, and other VDR connectors can be added to `.mcp.json` when partner URLs are available.
 

corporate-legal/skills/cold-start-interview/SKILL.md

@@ -146,7 +146,7 @@ If the answer is 3, add:
 
 #### What's connected?
 
-> This plugin can work with: VDR (Intralinks, Datasite, Box), board portal (Diligent, BoardEffect), document storage, and Slack. Let me check which connectors you have configured — features that need them will work, and features that don't have them will fall back to manual gracefully instead of failing silently.
+> This plugin can work with: VDR (Intralinks, Datasite, Box), board portal (Diligent, BoardEffect), document storage, document comparison (Version Story), and Slack. Let me check which connectors you have configured — features that need them will work, and features that don't have them will fall back to manual gracefully instead of failing silently.
 
 **Check what's actually connected, not what's configured.** A connector listed in `.mcp.json` is *available*. A connector that's actually responding is *connected*. These are different, and confusing them destroys trust. For each connector this plugin uses:
 

litigation-legal/.mcp.json

@@ -41,6 +41,12 @@
       "url": "https://mcp.trellis.law/anthropic",
       "title": "Trellis",
       "description": "The largest state trial court dataset in the U.S. — dockets, rulings, verdicts, filings, judge and opposing counsel analytics, expert witness vetting."
+    },
+    "Version Story": {
+      "type": "http",
+      "url": "https://mcp-compare.versionstory.com/mcp",
+      "title": "Version Story",
+      "description": "Deterministic document comparison — turn any two versions into Word tracked-changes or PDF redlines, merge parallel edits into one draft, build version histories with every change attributed."
     }
   },
   "recommendedCategories": [
@@ -49,6 +55,7 @@
     "case-law",
     "court-analytics",
     "outside-counsel-network",
+    "document-comparison",
     "documents",
     "chat"
   ]

litigation-legal/CLAUDE.md

@@ -91,6 +91,7 @@ This file is the house-level frame every matter is triaged against. Risk calibra
 | Gmail | [✓ / ✗] | Correspondence pulled manually; no automated history |
 | Scheduled-tasks | [✓ / ✗] | Deadline + hold-refresh reminders run on demand only |
 | CLM (Ironclad / Agiloft) | [✓ / ✗] | Contract pulls are manual for commercial cross-reference |
+| Document comparison (Version Story) | [✓ / ✗] | Version differences described in prose; no tracked-changes or PDF redline produced |
 
 *Re-check: `/litigation-legal:cold-start-interview --check-integrations`*
 

litigation-legal/README.md

@@ -125,10 +125,11 @@ The legal research connectors in this plugin aren't just data sources — they'r
 
 ## Integrations
 
-Ships with the general bucket of connectors in `.mcp.json`:
+Ships with the general bucket of connectors in `.mcp.json`, plus document comparison:
 
-- **Slack** — search messages, read channels, find discussions
-- **Google Drive** — search, read, and fetch documents
+- **Slack** — search messages, read channels, find discussions (general bucket)
+- **Google Drive** — search, read, and fetch documents (general bucket)
+- **Version Story** — redlines between document versions (settlement drafts, contested agreements, expert reports)
 
 Designed to be useful with nothing connected. If/when you want to pull from Relativity, DISCO, CLMs, or email, integration skills can be added without changing the core architecture.
 

litigation-legal/skills/cold-start-interview/SKILL.md

@@ -21,7 +21,7 @@ argument-hint: "[--redo | --check-integrations]"
 ## Flags
 
 - `--redo` — re-run the full interview and overwrite `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md`.
-- `--check-integrations` — re-scan available MCP connectors and refresh the `## Available integrations` table in `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` without re-running the full interview. Use after setting up a new connector (DMS, document storage, Gmail, scheduled-tasks, CLM).
+- `--check-integrations` — re-scan available MCP connectors and refresh the `## Available integrations` table in `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` without re-running the full interview. Use after setting up a new connector (DMS, document storage, Gmail, scheduled-tasks, CLM, document comparison).
 
 When probing: only report ✓ if an MCP tool call actually succeeded. Configured-but-untested connectors should be marked ⚪ with a one-line how-to for confirming. Never report ✓ based on `.mcp.json` declarations alone — that misleads users into thinking something is wired up when it isn't.
 
@@ -200,7 +200,7 @@ This refines escalation / supervision language in the practice profile:
 
 ### What's connected?
 
-> This plugin can work with: DMS (iManage), document storage (Google Drive, SharePoint, Box), Gmail, scheduled-tasks, CLM (Ironclad), eDiscovery (Everlaw, Relativity, DISCO, Aurora), legal research (CourtListener, Descrybe, Trellis), outside-counsel recommendations (TopCounsel). Let me check which connectors you have configured — features that need them will work, and features that don't will fall back gracefully instead of failing silently.
+> This plugin can work with: DMS (iManage), document storage (Google Drive, SharePoint, Box), Gmail, scheduled-tasks, CLM (Ironclad), eDiscovery (Everlaw, Relativity, DISCO, Aurora), legal research (CourtListener, Descrybe, Trellis), outside-counsel recommendations (TopCounsel), document comparison (Version Story). Let me check which connectors you have configured — features that need them will work, and features that don't will fall back gracefully instead of failing silently.
 
 **Check what's actually connected, not what's configured.** A connector listed in `.mcp.json` is *available*. A connector that's actually responding is *connected*. These are different, and confusing them destroys trust. For each connector this plugin uses: