Scrive MCP: connect Scrive to Claude and ChatGPT
Ask Claude or ChatGPT whether the Acme agreement is signed, who still hasn’t signed the new employment contracts or which documents are about to time out. The answer comes straight from Scrive, with a link to the document. No clicking through the archive.
With Deployed OS everyone connects with their own Scrive login. The AI sees the documents that person can see in Scrive, and nothing is created, sent or reminded.
2 read actions · read-only · Works in Claude, ChatGPT and Copilot
What your team can do with Scrive in Claude and ChatGPT
Signed or still pending
Contracts for new starters
Before a document times out
Signing status in one answer
Ask it like this
“Has Nordic Logistics signed the framework agreement yet? If not, who is missing?”
“Which documents are pending right now, and who is still to sign each one?”
“Which employment contracts sent this month have been opened but not signed?”
“Which pending documents expire in the next seven days?”
“List everything that was rejected or timed out since August, with the parties on each.”
“Give me the link to the signed NDA with Bergman & Co.”
What the Scrive MCP connector does today
- Reads
scrive_list_documentsList the documents you can see, latest change first, by status (in preparation, pending, closed when all have signed, cancelled, timed out, rejected) or words in the title, with how many have signed and who is still to sign. Up to 100 at a time.
- Reads
scrive_get_documentRead one document: title, status, dates, file name, every party with their role, when each one opened and signed it, and who is still to sign.
Need it to do more? We extend connectors for the companies that use them.
Who sees what
- Read-only
- The connector reads documents, their status and their parties. It cannot create, send or remind anything in Scrive.
- Each person’s own documents
- Everyone connects their own Scrive login, so the AI sees the documents that person can see in Scrive. HR’s contracts stay with HR.
- You choose who gets it
- Admins decide which groups at the company can use the Scrive connector at all. Everyone else never sees it.
- Every call logged
- Who asked, which connector, when. Deployed OS shows reads per connector and per person, and the log can be exported.
Set up the Scrive connector in three steps
Scrive’s own MCP server or Deployed OS?
Scrive has its own MCP server, aimed at developers and technical teams to start with. It lets an AI agent run Scrive’s signing flows, including ID-verified signing with eIDs such as BankID. If a developer wants to build agent workflows on Scrive, it is a good place to start.
Deployed OS is for when the whole company should use it. One company connection for all your tools, with each person on their own Scrive login, admins choosing which groups get Scrive, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.
Scrive MCP: common questions
Yes. Scrive has its own MCP server, built for developers and technical teams. Deployed OS gives the whole company the same connection, with each person’s own login, access per group and a log of every call.
No. The connector only reads. Nothing is created, sent or reminded. If you want it to do more, for example remind parties who haven’t signed, we can extend it for you.
Yes. Deployed OS is your company’s own MCP, so the same Scrive connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.
Yes. Your company registers its own OAuth2 client in Scrive, and Deployed OS reads through the Scrive API with each person’s own login. Claude and ChatGPT reach it via MCP.
Yes. The admin can register the client in Scrive’s API testbed and point Deployed OS at it for a trial. When you are happy, switch to production.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.
