Atlas MCP

Connect Atlas in your agent.

Ten MCP tools cover the full signing lifecycle. OAuth in Claude and ChatGPT. API key for Cursor and Claude Code.

Open in Claude Connect guide

Claude

ChatGPT

Cursor

Setup

Add Atlas in Claude.

Use the one-click link or paste the MCP URL manually. Start a new chat after you connect.

Connect in Claude Desktop

1Open Claude Settings → Connectors
2Add custom connector and paste the Atlas MCP URL
3Sign in to Atlas when prompted, then click Allow

https://atlaswork.ai/api/mcp

Open in Claude

Or copy the one-click setup link and paste it in your browser.

https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Atlas&connectorUrl=https://atlaswork.ai/api/mcp

Cursor and Claude Code

Dev tools use a Bearer API key in your MCP config. Sign up, copy your key from Settings, and point at https://atlaswork.ai/api/mcp.

Full connect guide (Cursor, VS Code, API key) · Dashboard copy-paste config

First message

Paste this in chat.

Agents prepare the envelope and return a review link. Signers get email only after you click Send on review.

I use Atlas for e-signatures. Draft a short contract in this chat, then use Atlas to prepare it for review (not send yet). Share the review link when it's ready. I'll click Send on the review page before anyone gets an email.

Send.

Finish the whole send in chat. Revise the contract, edit parties, fix fields, then send. You never leave the conversation.

Start

Ask to send. Stay in chat.

Tell your agent who signs. It reads the doc and places fields. You finish the job in the same thread.

Atlas MCP

via Claude

Send our mutual NDA to jane@acme.com. Jane signs first.

Reading the NDA and placing signature fields for Jane.

Draft is ready. Tell me if you want to change parties, dates, or fields.

Revise

Change what you need. Still in chat.

Change the effective date. Add a signer. Move a field. Each fix happens in chat. Open review, confirm, and send.

Atlas MCP

via Claude

Change effective date to July 1. Add bob@vendor.io as signer 2.

Updated. July 1 effective date. Jane signs first, then Bob.

Review link is ready. Open it, confirm everything looks right, and send.

Field detection

Fields land on the review page.

Atlas detects signature blocks, dates, and text fields in about 15 seconds. You review placement on the PDF, adjust if needed, then click Send.

Atlas MCP

via Claude

Are the signature fields detected on that NDA?

Yes. 8 fields across 2 parties are ready on the review page.

Open the review link, confirm placement, then click Send. Signers get email only after that.

While signers work

Track progress from the same thread.

Your agent can see who has signed and who is next. Send a nudge from the same thread without opening the dashboard.

Atlas MCP

via Claude

Has Jane signed the NDA yet?

Jane signed. Bob at bob@vendor.io is up next.

I can remind Bob or send you his signing link if you need to forward it.

Repeat sends

Fire the same NDA from a template.

Save a signed envelope as a template once. Send the same NDA again with one message. Ask to review first and no one gets email until you click Send on the review page.

Atlas MCP

via Claude

Send our standard mutual NDA to alex@newco.io. Let me review fields before signers get email.

Draft is ready from your mutual NDA template. Open the review page to confirm fields, then click Send.

Alex will get the signing email only after you send.

After signing

Pull structured contract data.

When every party has signed, your agent can pull key terms as structured data. Pipe it into your CRM, billing, or the next step in your workflow.

Atlas MCP

via Claude

The NDA is fully signed. What is the effective date and who signed?

Effective date is June 1, 2026. Jane Doe signed for Acme Corp and Bob Smith for Vendor LLC.

I have the full contract summary ready for your CRM or billing workflow.

Tools

Ten MCP tools for the full lifecycle.

send_contract_for_review

send_contract_from_template

get_envelope

check_signing_status

list_envelopes

list_templates

get_template

void_envelope

remind_signer

extract_contract_data

MCP getting started · Send NDA from Claude · Templates and workflows · API reference

FAQ

MCP questions.

https://atlaswork.ai/api/mcp. Paste it into Claude Settings → Connectors or your MCP client config.

Add https://atlaswork.ai/api/mcp as a custom connector in Claude or ChatGPT settings. Sign in with OAuth when prompted. Cursor and Claude Code use an API key in a config file.

Ten tools cover the full lifecycle: send for review, send from template, get envelope, check status, list envelopes and templates, void, remind, and extract signed data.

No for Claude and ChatGPT connectors. OAuth handles auth. Cursor and Claude Code need a Bearer API key from your dashboard settings.

Agents prepare the envelope and return a review link. A human clicks Send on the review page before any signer gets email.

Claude calls request_document_upload, you drop a PDF or DOCX in the upload page, then say done in chat. The agent completes the upload session and continues.

Ask your agent to list templates and call send_contract_from_template with the template id and signer emails. You still review before send. See the Templates page for use cases and workflow guides.

Set webhook_url at envelope create. Atlas POSTs lifecycle events like envelope.sent and envelope.signed with an HMAC signature in X-Atlas-Signature. See /docs/platform/webhooks-and-debugging.

Yes. All ten MCP tools work on the free tier. You get five free envelope sends. Drafts and field detection are unlimited.

The /mcp page lists all ten tools. For request shapes and examples, open /dev or the OpenAPI spec at atlaswork.ai/openapi.json.

Ready to send your first contract?

Five free sends. Connect Atlas to Claude in about a minute.

No credit card required to start.