Atlas API and MCP

REST API

Base URL: https://api.atlaswork.ai

Authenticate with an organization API key (format atlas_sk_...). Create and revoke keys in the dashboard. Pass the key as a Bearer token or in the x-api-key header.

Create and send a contract

Create an envelope from a document. Atlas detects the signature fields and returns a review URL along with the envelope ID.

curl -X POST https://api.atlaswork.ai/api/v1/envelopes \
  -H "Authorization: Bearer atlas_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "document": { "url": "https://example.com/nda.pdf" },
    "participants": [
      { "name": "Alice Chen", "email": "alice@example.com" }
    ]
  }'

Then dispatch it. The first signer gets email once you call send.

curl -X POST https://api.atlaswork.ai/api/v1/envelopes/{id}/send \
  -H "Authorization: Bearer atlas_sk_..." \
  -H "Content-Type: application/json" \
  -d '{}'

Write endpoints accept an optional Idempotency-Key header so a retried request cannot create or send twice.

Envelope endpoints

Template endpoints

Atlas does not push webhooks today. Poll GET /api/v1/envelopes/{id}/status for progress or read the event log at GET /api/v1/envelopes/{id}/events.

Full request and response shapes live in the OpenAPI spec.

MCP server

Endpoint: https://mcp.atlaswork.ai/mcp

A hosted MCP server over Streamable HTTP. Auth is OAuth 2.1 with PKCE and dynamic client registration: point your client at the endpoint, sign in when prompted, and approve the scopes. API keys are for the REST API only and are never entered into an MCP client. For new documents, agents prepare the envelope and return a review URL, and a human clicks Send before any signer gets email. Sends from a saved template go out on their own unless you pass auto_send: false.

Connect a client

• Claude: Settings, then Connectors, then Add custom connector. Paste the endpoint URL and sign in.
• ChatGPT: Settings, then Connectors, then Create. Paste the endpoint URL and complete the OAuth prompt.
• Cursor and other MCP clients: add the server block below to mcp.json and complete the OAuth prompt in the browser.

{
  "mcpServers": {
    "atlas": {
      "url": "https://mcp.atlaswork.ai/mcp"
    }
  }
}

OAuth details

Clients that support OAuth discover all of this from the endpoint. The 401 challenge points at the protected-resource metadata, which names the authorization server. You only need these values if you are wiring a client by hand.

• Issuer: https://app.atlaswork.ai/api/auth
• Metadata (RFC 8414): https://app.atlaswork.ai/.well-known/oauth-authorization-server
• Endpoints under the issuer: /oauth2/authorize, /oauth2/token, /oauth2/register, /oauth2/revoke, /oauth2/introspect
• Grants: authorization code with PKCE (S256), refresh token, client credentials. Response type: code.
• Scopes: envelopes:read, envelopes:write, documents:write, extract:read, offline_access. Read tools need envelopes:read. Write tools need envelopes:write.

Tools