Claude+E-Signatures

Claude and E-Signatures: What It Can Send, and From Where

How to turn on a signature provider's connector in Claude, such as Docusign's MCP server, what it can and cannot do, how to fix it when it stops working, and how to hand the whole job to The Drive AI from inside Claude.

The short answer

Claude has no electronic signature feature of its own. It can work with one through a connector: Docusign publishes an MCP server for its agreement platform, which you add as a custom connector and use with a Docusign account. The Drive AI's connector takes a different route: ask Claude to send a PDF that is already in your workspace for signature, and The Drive AI places the fields, shows you the draft, and sends it after you confirm. Signers need no account, and the signed, certified copy lands next to the original.

Set up

How to give Claude a signature provider on its own

01

Add the provider as a custom connector

On Pro and Max, open Customize, Connectors, then + Add and Add custom connector; enter a name and the server URL and review the sign-in it asks for. On Team and Enterprise, an owner adds it under Organization settings, Connectors, and each member then connects.

02

Sign in to the provider

Docusign's MCP server works against a Docusign account; its developer documentation names the server URL and the demo and production options. Claude asks for the sign-in when the connector is first used.

03

Turn it on in the chat

Click + at the lower left of the chat, choose Connectors, and switch the provider on for that conversation.

04

Review what you allow

Anthropic has not verified custom connectors and warns that, once connected, Claude can take action in the service. Only choose Allow always for tools you trust to run unsupervised.

What it does

What Claude can and cannot do with e-signatures

It can

  • Summarize your active agreements held in the provider
  • Trigger an agreement workflow the provider already defines, such as an NDA approval in Docusign Workflow Builder
  • Work in natural language against the provider's agreement and workflow features
  • Run on any Claude plan that can add custom connectors, which is all of them (Free allows one)

It cannot

  • Sign, send or track a document by itself; every signature action runs in the connected provider
  • Send a PDF that sits in your Google Drive, OneDrive or on your laptop without first getting it into the provider
  • Keep the signed copy next to the original in your drive
  • Work without a provider account and plan; the Docusign server is for Docusign customers

Troubleshooting

Claude will not send a document for signature?

Claude says it cannot send documents for signature

That is correct for Claude on its own. Add a provider's connector (Docusign's MCP server) or The Drive AI's, and turn it on in the chat under + and Connectors.

Add custom connector is missing

On Team and Enterprise only Owners and Primary Owners (or a custom role with Manage access to Libraries) add connectors, under Organization settings; members then connect to what was added. Free allows one custom connector.

The connector asks for a token or a demo account

Docusign's developer documentation distinguishes demo and production accounts; sign in with the account that holds the agreements you mean to work on.

The PDF is in my drive, not in the provider

Ask The Drive AI from Claude instead: it sends a file already in your workspace, places the fields by the signature lines, and shows you the draft before anything goes out.

Bigger jobs

Where it stops, and what The Drive AI adds

A provider connector lets Claude work on agreements that already live in that provider. The PDF most people want signed is in a folder, which is where The Drive AI starts.

JobClaude with a provider connectorWith The Drive AI
Send a PDF from your drive for signatureGet the document into the provider first.Name the file; the agent places the fields and shows you the draft. You confirm, it sends.
Where the signature fields goThe provider's templates and editor.Anchored to the page's own text ("Signature:", a party's name); adjust in the Sign editor before confirming.
Signing in orderDepends on the provider.Yes; a later signer is asked only after the earlier one has signed.
Who has signed, and whose turn it isYes, in the provider.Yes, from Claude: each recipient's state and the last reminder.
Remind or cancelYes, in the provider.Remind only the signers whose turn it is; void a request before it completes.
The signed copyStored in the provider.Certified and saved next to the original, in the same folder.
PriceThe provider's plan, often per envelope.Included with Max and Team, with no per-envelope fee.

Add The Drive AI to Claude

E-signature in The Drive AI comes with Max and Team, with no per-envelope fee. Signers need no account. Requests are sent from your workspace files, and the signed copy is saved next to the original.

Claude.ai and Claude Desktop

Open The Drive AI in Claude's connector directory, choose Connect and sign in. Connectors are on your account, so the desktop app gets it too.

Claude Code

claude mcp add --scope local --transport http thedriveai https://mcp.thedrive.ai/mcp

Server URL

https://mcp.thedrive.ai/mcp

Try it

Prompts for E-Signatures

Send the NDA in my Contracts folder to jordan@example.com and then to me for signature, with a signature and a date for each of us where the signature lines are. Show me the draft before you send it.

The request is prepared as a draft you see first; the send happens only when you confirm.

Who has signed the Northwind MSA, and whose turn is it?

The state of every recipient, from the assistant you are already in.

Remind whoever has not signed the office lease yet.

Only the signer whose turn it is hears from you; signers not yet reached are left alone.

FAQ

Common questions

Checked against the publishers' documentation and The Drive AI agent's own tool liston 2026-10-28. Sources:

Can Claude sign documents?

No. Claude has no electronic signature feature. It can work with a signature provider through a custom connector, such as Docusign's MCP server, or send a PDF from your workspace through The Drive AI's connector.

Can Claude send a document for e-signature?

Through a connector, yes. With The Drive AI added, ask Claude to send a PDF in your workspace to named signers; the agent places the fields, shows you the draft, and sends it once you confirm. Every signer gets an email with a personal link, and the certified copy is saved next to the original.

Is a signature sent through Claude legally binding?

The binding part is the provider's process, not Claude. Requests sent through The Drive AI keep an audit trail of who viewed and signed, and when, and electronic signatures are recognized under the U.S. ESIGN Act, eIDAS in the EU and equivalent laws in most countries.

Does the signer need an account?

Not with The Drive AI: signers receive an email with a personal signing link and confirm their identity with a one-time code. Provider connectors follow that provider's rules.

Which plan includes e-signature in The Drive AI?

Max and Team, with no per-envelope fee. Asking from Claude needs The Drive AI connector added, which any Claude plan can do.

Say it once, in the assistant you already use.

Ask The Drive AI directly, or add it to Claude and ask there. Either way the draft comes back for you to confirm before anything is saved or sent.