Scrive MCP overview

In one sentence

The Scrive MCP lets the AI assistant you already use, such as Claude, ChatGPT or Gemini, work with your Scrive documents on your behalf: find them, prepare them, send them for signature and follow up, all by asking in plain language.

What “MCP” means

MCP is short for Model Context Protocol. It is an open standard that gives AI assistants an agreed, safe way to use other products. Scrive runs an MCP server. Your assistant connects to it, learns what it is allowed to do in Scrive, and asks Scrive to do those things when you ask.

You do not need to know how the protocol works. If your AI tool can add a “connector”, “integration” or “MCP server”, it can use the Scrive MCP.

How it works

You add Scrive to your AI tool. In your assistant’s settings, add the Scrive connector. The address is https://mcp.scrive.com/mcp, and there is a step-by-step guide for each tool under Connect your AI tool.
You sign in to Scrive and approve. A normal Scrive sign-in window opens. You approve once, and your assistant gets permission to act as you, and nothing more.
You ask, the assistant does. “Send this NDA to Anna for signature” becomes the right sequence of steps in Scrive. Before anything is sent, cancelled or deleted, the assistant asks you to confirm.

Nothing to install

Scrive runs the MCP server. There is no software to download and no key to copy. If you can sign in to Scrive, you can connect.

Acts as you

The assistant can see and do exactly what you can in Scrive: your documents and your templates, with your permissions. Disconnect it from your AI tool at any time.

What you can ask for

You say	What happens in Scrive
“Send this NDA to Anna Lind for signature.”	The PDF is uploaded, Anna is added as a signer, and signing starts once you confirm.
“Which of my documents are still waiting for a signature?”	Everything pending is listed, with links.
“Remind everyone who hasn’t signed the supplier agreement.”	Reminders go out once you confirm.
“Create an employment contract from our standard template for Sam, signing with Danish MitID.”	A document is created from the template and Sam is added with the right eID.
“Download the signed contract with Acme.”	A download button appears for the sealed PDF.
“How many documents did we send last month?”	Your usage statistics are pulled and summarised.

More examples, grouped by team, are under Example use cases. The complete list of what the assistant can do is under Capabilities & tools.

What it will not do

It cannot see documents you cannot see, and it cannot change company or account settings.
It does not send, cancel or delete without asking you first, as long as you keep your AI tool’s confirmations on. They are on by default.

Your data

Whatever the assistant reads from Scrive, such as document titles, party names and email addresses, is handled by your AI provider (Anthropic, OpenAI, Google or another) under their terms and privacy policy, and that provider may be based outside the EU. The assistant’s answers are written by the AI provider, not by Scrive, so read anything important before acting on it.

For the technically curious

The Scrive MCP is a remote MCP server at https://mcp.scrive.com/mcp. It uses the Streamable HTTP transport and is protected by OAuth 2.0 with PKCE through oauth2.scrive.com. It keeps no state and stores no tokens: each request carries the signed-in user’s token and is forwarded to the Scrive API. Details are on Any MCP client and Access & permissions.

What comes next?

Connect your AI tool Guides for Claude, ChatGPT, Gemini, Copilot Studio and Slackbot, plus any MCP client.

Example use cases Ready-to-paste prompts for common workflows.

Access & permissions How sign-in works, what the agent can and cannot do, and rate limits.

FAQ Answers to common questions about permissions, data and setup.