How to Sign and Send Documents with Claude

Sending a contract for signature is a five-minute task that breaks your focus for twenty. You leave what you were doing, find the right template, retype names and email addresses you already have in front of you, and hope you picked the right document.

If you already work in Claude, that whole loop can happen in the conversation you are already having. This guide covers the setup and, more usefully, what the workflow actually feels like once it works — including the parts where Claude deliberately stops and asks you.

What you need

• A Signvoy account. The free plan works — MCP access is not gated behind a paid tier.
• At least one published template. Draft-only templates cannot create documents, and this is the single most common reason a first attempt fails.
• Claude Desktop, Claude on the web, or Claude Code.

Connect Claude

Signvoy's MCP server is remote and speaks streamable HTTP, so there is nothing to install.

Claude Desktop or Claude on the web: open Settings → Connectors → Add custom connector and enter:

https://api.signvoy.com/mcp

Claude Code: one command in your terminal.

claude mcp add --transport http signvoy https://api.signvoy.com/mcp

Either way, Claude opens a browser window asking you to sign in to Signvoy and approve access. Click Allow and you are connected.

That is the whole setup. There is no API key, because the server implements OAuth 2.1 with Dynamic Client Registration — Claude registers itself as a client and receives a short-lived token scoped to one workspace. For contrast, Docusign's connector requires you to create an Integration Key, generate a Client Secret, and paste Claude's two callback URLs into a Redirect URIs field before anything works. Signvoy asks for a URL.

The step-by-step version with screenshots of each screen lives in the Claude setup guide.

Verify it connected

Ask Claude something that requires a read tool:

What Signvoy templates do I have?

You should get back a list of template names. If you get "no tools available" or a 401, the troubleshooting guide covers the three failure modes that account for nearly all first-time problems.

The actual workflow

Here is a real sequence, and what Claude does behind each step.

Send the mutual NDA to Jane Doe at jane@example.com.

Claude calls signvoy_list_templates to find the NDA, then signvoy_get_template to read the template's recipient role keys. Role keys matter: a template might define signer and witness, and every recipient you supply has to match one. This is why Claude reads the template before drafting rather than guessing.

Then it calls signvoy_create_document — and stops.

What comes back is a draft. No email has been sent. Claude reports the recipient list and a review_url pointing at the document in your Signvoy dashboard, and asks whether to send it.

You open the link, confirm the document and the recipient, and reply:

Yes, send it.

Now Claude calls signvoy_send_document and Jane gets her signing email.

The two-call structure is deliberate. Create and send are separate tools specifically so that a model cannot email a counterparty from a single decision. An agent that misreads "draft an NDA for Jane" as "send an NDA to Jane" produces a draft you can delete, not a contract in someone's inbox. That matters more than it sounds like it does once an agent is reading your email — see human-in-the-loop AI contract signing for the threat model.

When the draft has a problem

If a recipient is missing an email address, signvoy_create_document still returns the draft, but with a send_blockers entry explaining what is wrong. Claude reads that and fixes it:

Jane's email should be jane.doe@example.com, not jane@example.com.

Claude calls signvoy_update_document with a corrected recipient list. One thing worth knowing: passing recipients replaces the entire list rather than merging, so Claude has to send every recipient, not just the changed one. It handles this correctly on its own, but it explains why a two-signer document briefly shows both people in the update call.

Following up

The read tools are where this saves the most time day to day, because checking on a signature is exactly the kind of interruption that isn't worth switching windows for.

Has Jane signed the NDA yet?

signvoy_get_document_status returns per-recipient state with timestamps — pending, signed or declined.

Nudge her.

signvoy_remind_document sends one reminder email to everyone still pending. Signvoy's tool description tells the model to use this sparingly and remind once rather than repeatedly, which is a small thing that stops an eager agent from becoming a nuisance to your counterparty.

Get me the signed PDF.

signvoy_get_signed_pdf_url returns a presigned download URL for the certified PDF. It expires after ten minutes by design, so ask again rather than saving the link.

You can also ask for the audit trail, which returns the append-only event log — send, view, sign, decline, void and remind events with actor, IP address and timestamp. Anything Claude did is tagged actorSource: "mcp", so agent activity stays distinguishable from your own dashboard activity months later.

Prompts that work reliably

Two patterns make a noticeable difference.

Name the template. "Send the mutual NDA to Jane" beats "send an NDA to Jane," because the second forces the model to choose between templates with similar names and it will sometimes choose wrong.

Supply the email address. Claude cannot invent a contact it has never seen. Giving it jane@example.com up front skips a send_blockers round trip.

The prompt library has copy-paste prompts for the common workflows, including the two prompts Signvoy registers on the server itself — which Claude Desktop surfaces as slash commands.

What Claude cannot do

Worth setting expectations. Claude can work with templates you have already built; it cannot design a new template or place signature fields on a PDF. Field placement is a visual task and stays in the Signvoy editor.

It also cannot void a document without you noticing — signvoy_void_document is marked destructive, so Claude prompts for confirmation before calling it, and voiding is irreversible.

Get started

Create a free Signvoy account, build one template, then paste https://api.signvoy.com/mcp into Claude. If you work in an editor rather than a chat window, the same server works in Cursor.