mdflows Request access

Help · AI apps

mdflows in ChatGPT and Claude

Describe an agreement or attach a PDF in a conversation, and mdflows prepares it for signature, sends it to your signers — one after another or all at once — and tells you who has signed, without leaving the chat.

What it does

  • Prepares documents. The assistant writes the agreement you describe; mdflows typesets it into a PDF and places a signature block for every signer. Or use a PDF you attach in ChatGPT, or one already in mdflows.
  • Sends them — in order or all at once. Each signer gets a secure, single-use email link when it is their turn — no account or download needed. They see where to sign, fill in anything you asked for (a job title, a date, initials, a tick box), and can draw their signature or simply type their name. You can sign yourself too, in mdflows.
  • Reuses your templates. Save a request as a template in mdflows — the document, the signer roles, the fields — and ask for it by name next time.
  • Tracks them. Ask where a request stands, remind whoever is waiting, fix a signer’s email, or cancel it. When everyone has signed, every party is emailed the signed copy with its Certificate of Completion.

What it will never do

  • Sign for anyone. Every signer — you included — signs on mdflows themselves, with a typed name (and, if they like, a drawn signature) and an explicit statement of intent.
  • Send without you. A request starts as a draft. Sending is a separate step your assistant asks you to confirm.
  • Delete anything, change your organization’s settings, or see other people’s requests.

Set it up

  1. An administrator turns on AI apps for the organization (Integrations → AI apps), after reading and accepting what connecting means. They can turn it off again at any time, which disconnects every app.
  2. Add mdflows to your assistant. In Claude: Customize → Connectors → Add custom connector. In ChatGPT: Settings → Apps → add an app (developer mode) — or find mdflows in each app directory once it is listed. Use this address:
    https://mdflows.com/mcp
  3. Sign in and approve. Choose your organization, sign in the way you always do (two-factor and single sign-on apply), and approve the connection. You need the designer role or higher to send documents.

Try asking

  • Draft a mutual NDA between Acme Consulting and Brightwater College and send it to amy@brightwater.edu for signature — I’ll sign first.
  • Turn this PDF into a signing request for the two contractors named in it — they can sign at the same time, and ask each for their company name.
  • Send my contractor agreement template to jo@example.com.
  • Who still hasn’t signed the vendor agreement? Send them a reminder.
  • Show me my signing requests from this week.

Limits

  • Up to 10 signers per request — one after another, all at once, or in rounds — up to 40 fields for them to fill in, and up to 9 people copied on the completion notice.
  • PDFs up to 20MB. Documents mdflows typesets use standard fonts, so their text must be in Latin script; for anything else, attach a PDF.
  • Signing links last 14 days by default (up to 90), and optional reminders go out on a schedule you choose.
  • Each request counts as one submission against your plan when it is sent.

Privacy and security

The connection uses OAuth: your assistant never sees your password, and mdflows stores only one-way hashes of its access tokens. The app can read your own signing requests — including document text and signers’ names and email addresses — and what it reads is also processed by the assistant’s provider under your agreement with them. Every action it takes is recorded in your organization’s hash-chained audit log as yours, with the app named. You can disconnect it at any time under Security → Connected AI apps. Read the privacy policy and the security overview.

Help

Write to help@mdflows.com.