You probably already have an AI assistant open for most of the day. It writes your emails, summarises long documents and helps you think through a negotiation. Until now, it knew nothing about the contracts you actually have. Today that changes: DottSign now has an MCP server, so Claude, Cursor, VS Code and other AI apps can work directly with your DottSign workspace.
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI apps connect to the tools and data you use. Instead of copying a contract into a chat window, you connect the app to DottSign once. From then on, when you ask a question about your contracts, the app looks up the answer in your workspace itself.
For you, that means no exports, no pasting and no guessing whether the AI is looking at the latest version of a document.
What you can ask
Once connected, you can talk to your contracts the way you'd talk to a colleague who has read all of them:
- "Which contracts expire or renew in the next 60 days?"
- "What's the notice period in our agreement with Acme?"
- "Who still hasn't signed the new NDA?"
- "List every payment obligation due this quarter."
- "Does the supplier contract have a liability cap? Quote the clause."
Behind the scenes, the AI app can search your contracts, read their full text, look up signers and their status, check obligations and key dates, review renewal history and see your plan usage. Answers come from your real documents, so you can ask it to quote the exact clause it relied on.
Draft a contract in the chat, file it in DottSign
Many contracts start as a conversation: "I need a simple service agreement for a two-month design project." Your AI app is good at drafting that first version with you. With the MCP server, it can also save the finished draft straight into DottSign as a new contract.
DottSign lays the text out as a clean PDF, with headings, numbered clauses and page numbers, and runs it through the same pipeline as any upload: encrypted storage, AI summary and automatic obligation extraction. The new contract counts toward your plan's monthly contract limit, just like one you upload yourself. Before sending it out, you open it in DottSign to place your signers' signature fields.
The AI app is instructed to show you the full draft and get your go-ahead before it creates anything.
You decide what it can do
When you connect an AI app, DottSign shows you a consent screen where you pick its permissions:
| Permission | What it allows |
|---|---|
| View your workspace (always on) | Search and read contracts, their text, signers, obligations, renewal history, notifications and plan usage |
| Create contracts | Save new contracts drafted with you |
| Edit contracts and obligations | Rename, tag and change the expiry date or status of contracts you own, manage obligations, and mark notifications as read |
| Send contracts for signature | Send contracts you own to their signers, who get an email from DottSign |
Leave everything except View unticked and the app can only look. Tick more when you're ready. To change permissions later, disconnect the app and connect it again.
Some things are never on the list. An AI app connected to DottSign cannot delete a contract and cannot sign anything on your behalf.
Built with security first
Connecting an AI app to your contracts should be as safe as signing in to DottSign yourself. Here's how we designed it:
- It sees only what you see. The AI app uses the same access rules as the DottSign web app. If you can't open a contract, neither can the app.
- Standard sign-in, no passwords shared. Connection uses OAuth 2.1, the same standard behind "Sign in with Google". You approve access on a DottSign screen, and the app never sees your password.
- Short-lived access. Access tokens expire after an hour and are renewed automatically in the background. We store them only in hashed form.
- Disconnect any time. Every connected app is listed in Profile → Integrations, with its permissions and when it was last used. Disconnecting cuts off access immediately. Resetting your password disconnects every app as well.
- Every change is on the record. Edits made through an AI app go through the same rules as edits in the web app: signed contracts stay locked, and changes land in the contract's history and audit log.
- Contract text is treated as data. The AI app is told to never follow instructions found inside a document, so a contract that says "ignore your previous instructions" is just text.
How to connect
The server URL is the same for everyone:
https://mcp.dottsign.com/mcp
Claude (claude.ai or Claude Desktop)
- Open Settings → Connectors and choose Add custom connector.
- Name it DottSign and paste the URL above.
- Click Connect, sign in to DottSign, choose the permissions and click Allow.
Claude Code
Run this in your terminal, then type /mcp in Claude Code to sign in:
claude mcp add --transport http dottsign https://mcp.dottsign.com/mcp
Cursor, VS Code and other apps
Add a remote MCP server with the URL above. Your app will open DottSign to ask for your approval. In Profile → Integrations, you'll find a step-by-step guide for each app, including one-click install links for Cursor and VS Code.
Availability
The MCP server is included on every paid plan: Starter, Pro, Business and Enterprise. If you're on the Free plan, you'll see an upgrade option when you open Profile → Integrations or try to connect an app.
To celebrate the launch, use the coupon MCP40OFF at checkout for 40% off your first 3 months on Starter, Pro, Business or Enterprise. It's valid until October 20, 2026.
What's next
This is the first version, and we want to hear how you use it. Tell us which questions you ask most, which actions you'd like your AI app to handle next, and which apps you're connecting. Head to Profile → Integrations in DottSign to connect your first AI app today.