Already using Scrive?
Start sending, signing and searching from your AI assistant. Free for all Scrive customers until end of year.
Get startedScrive MCP
Connect Scrive to Claude, ChatGPT or your own AI agent. Send agreements for signing and track them, verify identity with BankID and other eIDs, all without leaving the chat.
Your work has moved into AI. Now your agreements can too.
More and more work happens in AI assistants like Claude and ChatGPT: drafting, research, planning. That’s where the context for your agreements now lives, whether it’s a new deal, a new hire or the terms you just agreed on.
Scrive is how thousands of organisations get agreements signed securely, with verified identities such as BankID and MitID and a full audit trail behind every signature. With Scrive MCP, you get all of that directly from your AI assistant.
Upload your document or start from one of your Scrive templates, and your assistant adds the parties, sends it for signing and follows up, all in the same conversation.
A new way to start agreements. The same trusted signature.
Works where you already work
Send and track agreements from the AI tool your team already uses, without switching between tabs.
Just ask
Plain language instead of forms and clicks. Follow up in the same conversation: “Have they signed yet?”
The signature doesn’t change
The same eIDs, eIDAS signature levels, audit trail and archive as always. Your AI sets it up; people sign.
You need to accept marketing cookies to see the video.
Just ask. Scrive does the rest.
Pick your team and see what it looks like in practice.
Send this NDA to Anna Lind for signature.
Your assistant uploads the file, adds Anna as a signer and sends it once you confirm.
Send the order confirmation to Erik to sign with BankID.
The right eID is set for the signer automatically.
Which documents are still waiting for a signature? Remind everyone who hasn't signed.
You get a list of what's pending, and reminders go out to the ones you approve.
Has Acme signed the master agreement yet?
You see who has signed and who hasn't.
Create an employment contract for Sam from our standard template, signing with MitID, and send it.
Your template is filled in, the signer and deadline are set, and it's ready to go.
Set up onboarding for Sam: the contract and the IT policy, approved by our HR lead.
Both documents go out in one flow, with the right signer and approver.
Add the CEO as the final signer, after Sam.
The CEO is only invited once Sam has signed.
Which of our signed agreements mention automatic renewal?
Matching agreements, with links and the relevant passage.
Show everything we have with Nordic Logistics, newest first.
A full overview of that counterparty.
Change the signer on the supplier agreement to Kari Nordmann.
The party is updated without starting over.
How many documents did we send each month this year?
A monthly overview for the whole company.
How many documents were signed per day over the last two weeks?
Your signing pace, in seconds.
"You can always rely on the fact that the signed document is there. The Scrive archive is the source of truth for contracts."
Henrik Lie-Nielsen, Amp Eleven
Your AI, your choice
Scrive MCP works with the AI tool your organisation has already chosen. Whether that’s a commercial assistant, an enterprise deployment or an agent you've built yourself. Scrive doesn't run an AI model in the connection and never uses your agreement data to train one. Your assistant can only do what you can already do in Scrive, with the same access and permissions.FAQ
What is MCP?
MCP stands for Model Context Protocol, an open standard that allows AI assistants and agents to connect to external tools and services.
An MCP server acts as a bridge between an AI environment and a specific application.
Instead of asking an AI to tell you how to perform an action in another system, the AI can use connected tools to perform supported actions as part of a workflow.
The Scrive MCP server provides a standardised way for compatible AI environments to interact with Scrive’s agreement capabilities.
What is the Scrive MCP server?
The Scrive MCP server is an open-source Model Context Protocol server that allows compatible AI assistants and agents to interact with Scrive’s agreement capabilities.
It provides a standardised way for AI environments to search documents, create agreements, send signing requests, trigger reminders, check agreement status and perform other supported actions.
What can I do with the Scrive MCP server?
Depending on your setup, you can use AI to search and query agreements, create documents and bundles, add parties, send agreements for signing, trigger reminders and check agreement status.
Can Scrive MCP be used for electronic signatures?
Yes. Scrive MCP connects compatible AI environments to Scrive’s electronic-signature capabilities, allowing supported AI-driven workflows to create and initiate agreement signing processes.
Does using Scrive MCP change the signature in any way?
No. The MCP connection changes how an agreement workflow can be initiated and managed. The underlying Scrive signing infrastructure remains the same, including the applicable identity verification, eIDAS signature levels, hosting, audit trail and qualified trust service provider.
Does Scrive MCP support identity verification?
Scrive MCP can incorporate supported Scrive identity capabilities into AI-driven workflows. Available electronic identities depend on your Scrive setup.
What signature levels does Scrive MCP support?
Scrive provides electronic-signature capabilities aligned with the requirements of eIDAS. The specific signature and identity options available depend on the workflow and configuration.
See the developer documentation for current capabilities.
Which AI tools work with Scrive MCP?
Scrive MCP is designed for AI environments that support the Model Context Protocol. Current supported environments and setup requirements are available in the developer documentation.
Does Scrive MCP send my data to an AI model?
Scrive does not run an AI model as part of the MCP connection. Scrive MCP is designed to connect your chosen AI environment to Scrive’s agreement capabilities. The data-transfer behaviour of the AI environment itself depends on the environment and configuration your organisation has chosen.
Is Scrive MCP open source?
Yes. The Scrive MCP server is open source and available for developers to explore and use.
Is Scrive MCP the same as the Scrive eSign API?
No. The Scrive eSign API is designed for traditional software integrations where applications explicitly call API endpoints. MCP provides a standardised interface designed for AI assistants and agents to discover and use tools as part of a workflow.
Where can I find setup instructions?
See the Scrive MCP developer documentation for installation, configuration, supported environments and available tools.
I'm a Scrive partner, or want to become one. What does MCP mean for me?
Scrive MCP gives you one standard way to connect your agents, apps and services to Scrive. Your product can prepare, send and track agreements for signature, with secure eID signing built in, without building and maintaining a custom integration. That means you can bring new offerings to your customers faster. Interested in partnering with us? Get in touch and we’ll talk through what you’re building.
Receive Scrive MCP news & updates
If you are interested to be notified when there is a new update, tips or trick regarding Scrive MCP let us know by filling out the form.