Skip to main content
AI tools: use cases & prompts

MCP prompts for everyday contract work

Copy-ready prompts for Claude, ChatGPT and other AI tools connected to fynk: renewals, stuck contracts, counterparty briefings, NDAs, templates and data cleanup.

Written By Sebastian

Last updated About 2 hours ago

These prompts work in any AI tool connected to fynk via MCP. Copy one, adjust the names in brackets and send it. Your assistant only sees and changes what you can see and change in fynk.

Available on Essential, Business and Pro · Requires MCP

Before you start

  • Connect your AI tool first: Connect AI tools with MCP.
  • Use the names your account uses. If your contracts are grouped by tags, document types or teams, mention them, for example "supplier contracts tagged Purchasing".
  • Ask for a preview before changes: add "show me first, then ask before changing anything".

Find what needs attention

Renewal radar

Which contracts have a cancellation notice date in the next 90 days? Also list contracts whose notice date has already passed but which are still running.

You get: a list sorted by notice date with counterparty and link, plus a separate list of notice dates you may have missed.

Follow-up: Which of these renew automatically?

Stuck in review or signing

What's stuck in review or signing for [team], and what is each one waiting for?

You get: each document with what blocks it, for example a missing signatory or a signature that is still open.

Tip: limit it to a team, tag or the last 30 days. Checking many documents at once takes longer.

Counterparty briefing

Give me a briefing on everything we have with [company]: stage, key dates, values and anything still open. Include archived documents.

You get: all documents with this counterparty and the information stored in fynk. For questions about specific clauses, use the AI Assistant in fynk.

Create documents and templates

NDA ready for signature

Create an NDA with [company] from our [template name] template. The signatory is [name, email]. Show me what's missing, then ask me before you start signing.

You get: a draft with parties, signatories and fields filled in, and a check whether anything still blocks signing. Your assistant only starts signing after you confirm.

Check a template before you use it

Check our [template name] template: parties, mandatory fields, signature blocks and anything that looks inconsistent.

You get: a checklist, for example a select field with only one option, or a field that is optional but needed for a certain choice.

Turn an existing contract into a template

Turn this contract into a fynk template. Use our company as [role] and the other side as [role]. Make [start date, fee, notice period] fields and add signature blocks for both parties.

You get: an unpublished template with parties, fields and signature blocks. Review it in fynk before you publish it.

Keep your data clean

Find missing information

List signed contracts that have no end date and no expiration date.

Follow-up: Set the end date of [document] to [date]. Your assistant only changes the documents you name.

Add a metadata field

Add a metadata field for the payment term in days that the AI analysis fills in. Include English and German keywords.

Owners and Admins only. See Create custom metadata the AI can extract for good field descriptions.

Signed contracts report

How many contracts were signed in [month], by document type, and how long did signing take on average?

Good to know

Was this helpful?

Still need help? Ask the team