Integration
Claude, Cursor + Clinch: from chat to signed contract
Your AI assistant drafts the contract; Clinch gets it signed from your client's phone and requests the deposit.
Draft a contract freeHow it connects today
Official app not listed yetWorks today: paste or upload into ClinchThe Clinch MCP server (draft_contract, list_templates, use_template) is built but not yet published on npm, so it can't be installed yet. Today: paste the assistant's draft into Clinch with "Paste your own text".
Three recipes
Turn a client email thread into a contract
Ask Claude to draft a service agreement from the thread, paste it into Clinch, add the client and send it for signature.
Start from a template, filled in by the assistant
Pick one of the 50 free templates (web design, NDA, SOW, retainer…) and let the assistant fill it with the deal details before you send it.
Draft the contract next to your code
In Cursor, have the assistant write the statement of work from your project README, then send it with Clinch for signature and a deposit.
Set it up
- Ask Claude or Cursor to draft the contract: parties, scope, price, deposit, deadlines, revisions.
- In Clinch, open New contract and choose Paste your own text.
- Paste the draft, review it, add the client's name and email and an optional deposit.
- Send: the client signs from their phone, no account, and the deposit request goes out at signature.
Questions
Can I install the Clinch MCP server now?
Not yet: it is built but not published. This page will show the one-line install when it is.
Will the assistant send contracts on my behalf?
No. The MCP server only prepares a link that opens the draft in Clinch; nothing is sent until you review it and press send.
Does the MCP server need an API key?
No. It builds links to Clinch; your account is only involved when you open the link.
Close your next deal with Clinch
Describe the deal, get a contract, send it. Your client signs from their phone without an account. Free for 3 contracts a month.
Draft a contract free