Once the Scrive MCP is connected to your AI client, you can ask it to handle these tasks directly. Paste any of the prompts below into your chat to try it.
An agent can only do what you can already do in Scrive, so the documents it sees and the eID methods it can set depend on your account. See Access & permissions.
“Create an employment contract from our ‘Standard employment’ template for Sam Rivera, sam@example.com, signing with Danish MitID. Give it a 14-day deadline and send it.”
Onboarding flow
“Set up an onboarding flow for Sam Rivera: the employment contract and the IT policy, both signed by Sam and approved by our HR lead Maria Lopez, maria@example.com.”
Sequential signing
“Add the CEO as the final signer on the contract with Sam, after Sam has signed.”
Download the signed copy
“Download the signed employment contract for Sam Rivera.”
Give parties completely: full name, email, role (signer, viewer or approver), and the eID method if one is required.
Say when to send: the agent prepares first and asks before start_signing, start_flow, remind_document or cancel_document. Say “prepare but don’t send” if you want to check first.
Name the template when creating from one; the agent looks it up among your templates.
Use search for meaning, list for structure: “agreements that mention indexation” is a search_by_contents; “documents pending since March” is a list_documents with filters.
Uploads happen in a panel: when the agent needs a PDF from your computer, a file picker appears in the chat. Pick the file there.