Atlas MCP server for e-signatures

You want to know where the Atlas MCP server lives, what it exposes, and how to authenticate.

Short answer: https://atlaswork.ai/api/mcp. Ten tools. OAuth for Claude and ChatGPT. Bearer API key for Cursor, Windsurf, Cline, Continue, and VS Code.

> Share: "Atlas MCP endpoint: atlaswork.ai/api/mcp. Ten lifecycle tools."

Endpoints worth bookmarking

Authentication modes

OAuth (ChatGPT, Claude Desktop)

User signs in through the client. Atlas issues tokens via standard OAuth flows advertised in metadata. No API key in chat.

Bearer API key (IDE agents)

{
  "mcpServers": {
    "atlas": {
      "url": "https://atlaswork.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Generate keys in dashboard Settings.

Tools exposed

1. send_contract_for_review
2. send_contract_from_template
3. get_envelope
4. check_signing_status
5. list_envelopes
6. list_templates
7. get_template
8. void_envelope
9. remind_signer
10. extract_contract_data

Upload session helpers appear inside send_contract_for_review when request_document_upload is true.

Deprecated tool names return explicit errors. Update old prompts that reference upload_document or get_signed_pdf.

Response shape you should expect

Create paths return at minimum:

{
  "envelope_id": "uuid",
  "review_url": "https://atlaswork.ai/review/uuid?rt=..."
}

Status polls return signing progress without full envelope payload. Use get_envelope when you need download links.

Review policy

The Atlas MCP server returns review_url on new uploads. Email to signers fires after Send on that page. Template sends may auto-send when configured.

Client-specific setup links

• Claude
• ChatGPT
• Cursor
• VS Code

Hosting model

Atlas hosts the MCP server. There is no downloadable MCP binary to run on your VPC today. If you need air-gapped signing, REST plus your own storage may fit better than MCP.

Versioning the MCP manifest

Atlas may add tools over time. Clients call tools/list at connect time. Pin internal runbooks to tool names, not numeric counts, when you document agent playbooks.

Health check

Send a no-op status read against a known envelope id after config changes. If auth fails, Atlas returns a clear 401 before you attempt a client-facing send.

Relationship to atlaswork.ai REST

The MCP server and REST API share envelope rows. You can create via MCP and poll via REST in the same workflow without sync lag beyond normal database read consistency.

Monitoring in production

Log envelope ids from MCP responses in your observability stack. Correlate with webhook deliveries for signed events.

Uptime expectations

Atlas MCP runs on the same production API as REST. Monitor https://atlaswork.ai/api/mcp from your synthetic checks with a read-only tool call after auth.

Change management

Subscribe to Atlas changelog for new MCP tools. Update agent prompts when tools list grows.

Support path

If tools/list returns empty after auth, verify Bearer token or OAuth grant has not expired.

SLA-minded teams

Track p95 latency from tools/call create to review_url return. Large PDFs and cold detection increase tail latency. Warm templates skip detection on repeat sends.

IP allowlisting

Atlas MCP is public HTTPS. IP allowlisting is not required. Auth is Bearer or OAuth token based.

Disaster recovery

Export envelope ids and webhook logs to your warehouse. Recreate downstream state from Atlas GET if internal dashboards drift.

Incident response

If MCP auth fails globally, check status page and rotate API keys if compromise suspected. Envelope data remains in dashboard independent of MCP session.

Document the Atlas MCP endpoint in your internal runbook next to production API base URLs so on-call engineers find signing tools during incidents.

Operators sometimes confuse the marketing hub at /mcp with the JSON-RPC endpoint at /api/mcp. Link both in onboarding docs: humans read the hub, agents call the API path.

Compare latency between MCP tools/call and equivalent REST routes when debugging slow creates. Both hit the same envelope service.

FAQ

Does Atlas accept PDF and DOCX?

Yes. Upload either format when you create an envelope. DOCX files become PDF before anyone signs.

How do I sign in?

Use a Bearer API key from your dashboard settings. MCP connectors in ChatGPT and Claude use OAuth instead.

When do credits get used?

One credit per send, not per upload. You get five free sends when you sign up.

Where should I start?

/mcp and API reference.

Related reading

• MCP setup
• E-signature API guide
• MCP electronic signatures