Draftable

@Draftable list all document comparisons from the last 7 days, show me which ones are still processing

Found 12 comparisons in the past week. 10 are complete, 2 are still processing. Completed comparisons include: 'Q4_Budget_v1_vs_v2' (PDF, 47 changes detected), 'Employee_Handbook_Draft_vs_Final' (DOCX, 23 changes), 'Terms_of_Service_Update' (PDF, 8 changes). The two processing comparisons are 'Annual_Report_2024' (started 4 minutes ago, comparing 180-page PDFs) and 'Contract_Amendment_B' (started 12 minutes ago). All completed comparisons have viewer URLs available.

This example shows the MCP's core list-and-filter capability. Useful for auditing comparison history or checking job status. Requires API key with read access. The MCP returns metadata only — you'll need to visit Draftable's viewer URLs to see the actual side-by-side diff. Pagination means large comparison histories may require multiple queries.

@Draftable find the comparison for 'Merger_Agreement_Final' and tell me how many changes were detected between versions

Located comparison 'Merger_Agreement_Final_v3_vs_v4' completed 2 days ago. Draftable detected 34 changes between the two PDF versions: 18 text modifications, 9 deletions, 7 additions. The comparison took 8 seconds to process. Both source documents were 42 pages. The viewer URL shows changes highlighted across sections 3.2 (indemnification clauses), 5.1 (payment terms), and 7.4 (termination conditions). No formatting-only changes were flagged.

Demonstrates search-by-name within your comparison history. The change count comes from Draftable's diff engine, which is particularly strong with legal and financial documents. This example assumes the comparison already exists — the MCP cannot create new comparisons, only retrieve existing ones. Change counts are estimates; complex formatting can affect accuracy.

@Draftable show me all comparisons where the right-side document was uploaded in the last 48 hours, then summarize what types of documents my team is comparing most

Found 8 comparisons with right-side uploads in the last 48 hours. Document types: 4 PDFs (contracts and proposals), 3 DOCX files (policies and reports), 1 PPTX (pitch deck). Most active comparison pattern: contract revisions, with 5 of 8 comparisons involving legal agreements. Average processing time was 6 seconds. Three comparisons show high change density (>50 modifications), suggesting substantial redlines. Two comparisons are between nearly identical files (2-3 changes each), likely final proofreading passes.

This synthesis example pairs the MCP's list capability with AI reasoning to surface usage patterns. Helpful for team leads tracking document review velocity. The MCP provides raw comparison metadata; the AI infers patterns from file types, timestamps, and change counts. Accuracy depends on consistent file naming conventions in your Draftable account.

When legal ops needs a single-source comparison history

A 3-person legal ops team at a Series B SaaS company runs 40-60 vendor contract redlines per quarter. They store final PDFs in Google Drive, but lose the audit trail of what changed between drafts. The Draftable MCP solves this if you already use Draftable's comparison API to generate those redlines—List Comparisons pulls the history into Switchy so the team can ask 'show me all MSA changes from Q1' or 'which vendor pushed back on liability caps'. The threshold: this only works if you're creating comparisons via Draftable's API in the first place. If you're doing ad-hoc uploads through their web UI, the MCP won't surface those. For teams running a structured contract workflow where every draft gets compared programmatically, this turns comparison metadata into a queryable knowledge base.

Tracking policy updates across regulatory cycles

A 6-person compliance team at a fintech maintains 20 internal policies that get revised twice a year for SOC 2 and state licensing audits. They use Draftable to compare each policy draft against the prior approved version, but the comparison records live in Draftable's dashboard—siloed from the rest of their audit prep in Notion and Slack. The MCP bridges that gap: List Comparisons lets the team pull comparison metadata into Switchy and cross-reference it with audit checklists. The catch is the single-tool limitation—you can list comparisons but not retrieve the actual diff content or create new comparisons from Switchy. This works if your workflow is 'generate comparisons in Draftable, then query the list to confirm coverage'. If you need to kick off new comparisons or read the diffs inline, you'll still need the Draftable UI.

When engineering needs a diff history for requirements docs

A 5-person product engineering pod ships features every two weeks and maintains a 40-page requirements doc in Confluence. The PM updates the doc mid-sprint as scope shifts, but engineers lose track of what changed since the last standup. If the team runs Draftable comparisons on each doc export (PDF or Word), the MCP can surface that history in Switchy—'show me all spec comparisons from the last sprint' becomes a one-line query. The limitation: this assumes someone is already running those comparisons and that the team cares more about the list of changes than the inline diff content. For teams doing lightweight spec updates where a simple 'what changed' list is enough, this works. If you need to read the actual redline or compare on-demand without leaving Switchy, the single-tool MCP won't cover it.