Skip to content
BTS 2026Met us at the summit?Claim your summit offer
Works with Claude, ChatGPT and Cursor

Send and Track Agreements From Claude, ChatGPT or Cursor

FlowVerify runs a remote MCP server at mcp.flowverify.co. Connect a client with your own API key or by signing in, and it can find templates, prepare drafts, send, remind and download, inside the mandate an admin issued. Send, remind and void return a preview until the call carries an explicit confirm, and every action is recorded.

  • Send, remind and void need a confirm
  • Outside the mandate, a call is refused
  • It never signs for anyone
ClaudeFlowVerify connected
Send the vendor NDA to Farah Qureshi at Nandi Freight. Aadhaar eSign, due Friday.
FlowVerifysend_from_templatePreview only

Here is what I will send. Nothing goes out until you confirm.

Template
Vendor NDA
Recipient
Farah Qureshi · [email protected]
Signing
Aadhaar eSign
Deadline
Fri, 20 Nov 2026
EditConfirm & Send
Confirmed by you
FlowVerifysend_from_templateconfirm: trueSendingSent

Sent. Farah Qureshi has the signing link, and the reference is FV-2611-102.

Mandate “Procurement agent” · 4 of 20 sends used today · preview required

The tools

The Working Set, One Tool per Job

Each tool wraps a call of the public API and needs the same permission as that call. These fourteen cover a document from template to signed copy. The guide lists all 23.

Reads
Returns a short summary. No phone numbers, one-time codes, signing links, secrets or document text.
Changes a draft
Touches drafts only, and can be run as a dry run that returns the exact call it would make.
Needs a confirm
Returns a preview of who will be emailed and what would block it, unless the call says confirm: true.

Find

  • list_templatesReadsReusable templates and the roles to fill
  • list_envelopesReadsEnvelopes by status, name, recipient or tag
  • get_envelope_statusReadsWho has signed, the deadline, what can happen next

Prepare

  • create_envelopeChanges a draftA draft with its recipients. Nothing is sent
  • add_fileChanges a draftAttach a PDF or Word document to a draft
  • place_fieldsChanges a draftSignature, date and text fields on the pages

Send and Follow Up

  • send_from_templateNeeds a confirmFill a template’s roles and send it
  • send_envelopeNeeds a confirmCertify the documents and email the signers
  • remind_envelopeNeeds a confirmEmail signers who have not signed yet

Close Out

  • void_envelopeNeeds a confirmCancel a sent envelope. It cannot be undone
  • get_audit_trailReadsEvery recorded action, with who and when
  • download_signed_pdfReadsThe signed PDF and the certificate of completion

Negotiate

  • propose_termsNeeds a confirmOpen a negotiation on a draft’s clauses
  • respond_to_negotiationNeeds a confirmAnswer the other side’s wording where it is your move

Resources

Live data a client can attach to a conversation.

  • flowverify://templates
  • flowverify://envelopes/recent
  • flowverify://envelopes/{id}/certificate

Prompts

Ready-made tasks with the confirmation step built in.

  • send_for_signature
  • chase_pending
  • summarise_status

Safety by design

One Tool, Four Calls, and Where Each One Stops

The same tool is called four times below. Only one of the four sends an email, and that one carries an explicit confirm inside a mandate.

Preview, Then Confirm

Every tool that changes something can be run as a dry run. Send, remind and void return a preview unless the call says confirm: true.

A Repeat Is Not a Second Send

Creates and sends carry a key derived from the call itself. An agent that repeats a timed-out call gets the first result back.

The Mandate Decides

The mandate travels with every call. What it does not allow is refused with the reason, and the agent is told to stop, not to retry.

It Holds No Data of Its Own

The server has no database. Your key is read from each request and passed on, never stored. Results leave out document text, phone numbers and one-time codes.

It Never Signs for Anyone

No tool signs, forwards a signing link or handles a one-time code. Signers sign in the signer app, with the verification the sender chose.

A Test Mode That Sends Nothing

With a test key, no email, SMS or WhatsApp message goes out and nothing is charged. Test documents stay apart from live ones.

Connect

Three Steps to Connect a Client

The server speaks MCP over Streamable HTTP at mcp.flowverify.co/mcp and takes an API key or a sign-in. Start with a test key and nothing real is sent.

  1. Get a Credential

    Create an API key under Developers, API keys, with the scopes the agent needs. It is shown once. A connector in Claude or ChatGPT needs no key: you sign in.

  2. Issue a Mandate

    In the Agents console, choose the templates, the actions, the recipients and the daily cap. Copy the mandate id.

  3. Add the Server to Your Client

    Paste the address, and for a key the two headers. The agent can read its own limits and today’s usage before it acts.

Claude on the web and desktop: sign in

Connector address
https://mcp.flowverify.co/mcp

Add FlowVerify as a connector with this address. Claude sends you to FlowVerify, where you sign in and approve the connection. No API key is involved.

Claude Code: your own API key

Terminal
claude mcp add --transport http flowverify https://mcp.flowverify.co/mcp \
  --header "Authorization: Bearer fv_live_xxxxxxxx" \
  --header "X-Agent-Mandate: <mandate id>"

Two ways in

An API Key, or a Sign-In

Both reach the same tools and are held to the same limits. The difference is where the credential lives and who approves it.

The two ways to connect an MCP client: your own API key, or signing in
SuitsAPI keyCursor, Claude Code, VS Code and agents you buildSign-inConnectors in Claude and ChatGPT
CredentialAPI keyAn fv_live_… or fv_test_… key in the client’s config. The server forwards it and never stores itSign-inNone to copy. A person signs in to FlowVerify and approves the connection
PermissionsAPI keyThe scopes you gave the keySign-inTicked on the consent screen. Reading is always included
MandateAPI keyThe X-Agent-Mandate headerSign-inChosen on the consent screen, and changeable later without connecting again
Test modeAPI keyUse a test keySign-inChoose Test mode when you approve
To end itAPI keyRevoke the key or the mandateSign-inDisconnect under Agents, Connected apps

Who did what

Every Call Carries the Client’s Name

The server passes on the name and version of the client behind each call. The Agents console lists every agent that has called your workspace, with its credential, its mandate and when it was last seen.

These clients are recognised by name. Any other MCP client appears under the name it declares.

  • Claude
  • ChatGPT
  • Cursor
  • Gemini
  • Copilot
Where each action is recorded

FAQ

Questions About the MCP Server

Something else on your mind? Book a demo and ask us.

It can find templates and envelopes, create and prepare drafts, send from a template, check signing status, send reminders, void an envelope, download signed PDFs and certificates, and propose or respond in a clause negotiation. It can do only what the API key’s scopes, or the permissions approved at sign-in, allow, and only inside its mandate.

Three things. Send, remind and void return a preview unless the call carries an explicit confirm, so a well-behaved assistant shows you the preview and asks first. A mandate can require that preview before every send. And the mandate’s limits on templates, recipients and the daily cap are checked on FlowVerify’s side, where the agent cannot change them.

FlowVerify decides what each tool returns: names, statuses, recipients, dates and audit entries, as short summaries that leave out phone numbers, one-time codes, signing links, secrets and document text. A PDF reaches the app only when it asks to download one, and a mandate can leave downloading out. Once a result reaches the AI app, that app’s own terms apply to it.

No. The server has no database of its own. Your API key is read from each request, passed to the FlowVerify API and never stored or logged. When you connect by signing in instead, no key exists to store: the connection is a workspace record you can disconnect.

Someone allowed to manage agents in your workspace, who confirms who they are again unless they signed in within the last 10 minutes. By default the app’s access lasts 60 minutes at a time and renews only while it is used. The connection ends after 30 days without use and after 180 days in any case, and when the person who approved it leaves the workspace or loses that permission. You can disconnect it at any time under Agents, Connected apps.

Each action appears in the document’s audit trail with the name of the client that made it. Under a mandate it is also recorded against the agent and the person who issued the mandate, listed in the run log, carried on webhook events and printed on the certificate of completion.

Book a demo

See It on Your
Own Agreements

Tell us which client your team uses. We connect it to a test workspace with you, send a document from a conversation and show you the audit trail.

What you get

  • A live walkthrough on one of your own agreements
  • A workspace set up for your team
  • Answers from the people who build it