Prompt Multi-domain Claude · GPT-4 · MCP

Best Prompts & MCP of the Week — May 18, 2026

This week: a contract risk scanner for legal teams and the Filesystem MCP server for secure document workflows.

Prompt of the week

Contract Risk Scanner: Flag Obligations, Deadlines, and Liability Exposure

What it does: Analyzes any commercial contract and returns a structured risk briefing organized by severity, surfacing hidden obligations, auto-renewal traps, indemnification asymmetries, and hard deadlines. Built for in-house legal, procurement, and finance professionals who need a fast first-pass review before escalating to outside counsel.

When to use it:

  • Reviewing a vendor MSA or SaaS subscription agreement before signing
  • Auditing a batch of legacy contracts ahead of a renewal cycle
  • Preparing a risk summary for a CFO or GC before a board presentation

The prompt:

You are a senior commercial contracts attorney performing a pre-signature risk review. Analyze the contract text I provide and return a structured report with the following sections:

  1. CRITICAL RISKS — clauses that create significant financial, legal, or operational exposure (e.g., uncapped liability, unilateral amendment rights, broad IP assignment). For each: quote the relevant language, explain the risk in plain English, and suggest a negotiation ask.

  2. DEADLINES & NOTICE WINDOWS — every date, notice period, and time-triggered obligation. Format as a table: Clause | Obligation | Deadline | Party Responsible.

  3. AUTO-RENEWALS & TERMINATION TRAPS — identify renewal mechanics, termination-for-convenience restrictions, and any lock-in provisions. Flag if notice windows are unusually short.

  4. INDEMNIFICATION & LIABILITY — map who indemnifies whom, any carve-outs, and whether liability caps are mutual or one-sided.

  5. MISSING STANDARD PROTECTIONS — note any clauses that are absent but typical for this contract type (e.g., no limitation of liability, no governing law clause).

  6. EXECUTIVE SUMMARY — three bullet points a CFO could read in 60 seconds.

Contract type: [CONTRACT TYPE] Our company is: [YOUR COMPANY NAME AND ROLE — buyer/seller/licensor/licensee] Key concern: [OPTIONAL — e.g., “we are a small vendor, watch for enterprise-friendly asymmetries”]

[PASTE CONTRACT TEXT HERE]

Tips:

  • Paste one contract section at a time if the document exceeds 4,000 words; start with the definitions and liability sections, which carry the most risk density.
  • Add “Flag any references to governing law outside our jurisdiction: [YOUR JURISDICTION]” to catch cross-border enforceability issues.
  • Run the output through your GC as a starting checklist, not a final legal opinion — this prompt accelerates review, it does not replace it.

MCP deployment of the week

Filesystem MCP Server

What it does: The official Filesystem MCP server gives Claude secure, permission-scoped read and write access to folders on your local machine or a network drive. You define exactly which directories are accessible — nothing outside that boundary can be touched. It integrates directly into Claude Desktop or any MCP-compatible client, so the AI can open, read, summarize, compare, edit, and save files without manual copy-paste.

Best for: Operations and HR managers who maintain large libraries of policy documents, templates, or onboarding materials and need the AI to work across multiple files in a single session rather than one document at a time.

How to deploy:

  1. Install Claude Desktop (if not already running) and confirm it supports MCP servers — go to Settings → Developer → MCP Servers to verify the interface is available.
  2. Add the Filesystem server to your Claude Desktop config file by specifying the server path and the exact local directories you want to expose — for example, your HR policy folder or your contracts archive. Restrict access to only the folders relevant to the task; do not expose root directories.
  3. Restart Claude Desktop, open a new conversation, and test with a simple instruction: “List all files in the policies folder and tell me which ones haven’t been modified in over 12 months.” Claude will read the directory live and respond with real data.

Why it matters: Most professionals waste significant time moving content between tools — downloading a file, pasting it into a chat window, copying the output back, saving it manually. The Filesystem MCP server collapses that loop entirely. An HR manager can ask Claude to compare this year’s employee handbook against last year’s version, flag changed sections, and draft a summary of revisions — all from a single prompt, with the files read and written in place. For operations teams managing dozens of SOPs or IT teams auditing configuration templates, the productivity delta is immediate and requires zero developer involvement to set up.


Also worth trying

The “Assumption Audit” Prompt for Financial Models. Ask Claude: “Review the following financial model assumptions. For each, tell me: what real-world condition must be true for this assumption to hold, what is the most likely way it breaks, and what is the directional impact on the output if it does.” Paste your assumptions table — growth rate, churn, margin targets — and you get a structured stress-test brief. Finance and FP&A teams use this before presenting forecasts to the board to pre-empt the hardest questions.

Memory MCP Server for Recurring Client Work. The official Memory server gives Claude a persistent knowledge graph that survives across sessions. Connect it and instruct Claude to remember client preferences, standing instructions, and past decisions — “Always flag GDPR implications for EU clients” or “This client’s tone preference is formal, no contractions.” Account managers and legal ops teams handling the same clients repeatedly get an AI that behaves like a briefed colleague rather than starting cold every conversation. Deploy from the MCP reference repo alongside Filesystem for a powerful paired setup.

The “Policy-to-Plain-English” Prompt for HR. Use this one-liner for any internal policy document: “Rewrite the following HR policy as a plain-English FAQ. Use a question-and-answer format. Anticipate the five most common questions an employee would ask after reading this policy, answer each in two sentences or fewer, and flag any section that is ambiguous or likely to generate follow-up questions.” Paste in your PTO policy, travel expense rules, or code of conduct. The output is ready to drop into your intranet or onboarding deck with minimal editing.