How to send a contract from Claude

Claude can prepare an envelope, but Atlas will not email signers until you approve on the review page. That split keeps agents useful without bypassing human control.

Negotiation often finishes in chat. Sending should not require a separate SaaS tab unless you want it to.

> Share: "Claude prepares the envelope. You click Send on review. Signers get email after that."

Connect once

1. Open Claude Settings → Connectors.
2. Add a custom connector with URL https://atlaswork.ai/api/mcp, or use the one-click install.
3. Sign in to Atlas when OAuth prompts you.
4. Start a new chat so tools load.

Claude Desktop uses OAuth. Claude Code and Cursor need an API key in a config file instead. See MCP overview for client differences.

Prompt shape

Give the agent signer emails, roles if you know them, and how you have the document:

Send this MSA for signature with Atlas.

Signer: jane@acme.com, Jane Signer, Customer.

I have a local PDF. Give me an upload link.

Do not drag a PDF into Claude Desktop and expect it to forward the bytes. That path fails. Ask for an upload link.

Upload session flow

1. Claude calls request_document_upload.
2. You open the URL and upload PDF or DOCX.
3. Back in chat, say "done" or "uploaded".
4. Claude completes the session and returns review_url.
5. Open review, fix fields or parties if needed, click Send.

ChatGPT can often attach a file in chat. Claude cannot. Use the upload session for local files.

After Send

Ask Claude to check_signing_status or get_envelope. When status is signed, download the signed PDF from the envelope record if you archived it.

For the same NDA every week, save a template and use send_contract_from_template. Template sends may use auto-send when you trust the pinned fields.

Troubleshooting

Upload session failed. You skipped the link, used the wrong file type, or did not confirm in chat.

No email yet. You have not clicked Send on review. Agents cannot bypass that for new uploads.

Fields look wrong. Edit on review before Send. Detection is free to re-run from the dashboard if needed.

Repeat sends and the trust ladder

Once an NDA or SOW works, pin it as a template from the dashboard. In chat, ask Claude to list_templates, then send_contract_from_template with signer emails.

Ad-hoc uploads: review every time. Templates: auto-send when legal approved the shape once. That ladder is product policy, not a limitation.

Security note

OAuth connectors are the right path for Claude Desktop. Do not paste API keys into chat. Cursor and Claude Code keep keys in local config files only.

Public URLs

If the contract already lives on HTTPS, give Claude the URL in your prompt. The agent can pass document_url without an upload session. Make sure the URL is a direct download, not a login wall.

Multi-party prompts

List signers in order when the contract requires sequential signatures. Example: "Signer 1: bob@vendor.com. Signer 2: jane@acme.com after Bob signs." Atlas promotes the next party automatically when the prior signer finishes.

Testing before client sends

Create a test envelope with your own email as signer. Walk through upload, review, send, and sign on mobile. Confirm field visibility per party. Only then reuse the same prompt pattern for client documents.

Credits

Drafts and detection are free. Send consumes one credit. Atlas grants five credits on signup. Resends on an already-sent envelope do not charge again.

FAQ

Can Claude click Send for me? On new uploads, a human should open review and Send. Templates may auto-send when trusted.

What file types work? PDF and DOCX on every upload path.

Where is the full MCP tool list? MCP electronic signatures and /docs/mcp/connect.

More resources

• Send from Claude doc

-

Related reading

Next reads that match this topic: Bulk send with DocuSign: limits, CSV flow, an…, How bulk send works inside DocuSign, and DocuSign Bulk Send feature explained.