Skip to main content
Atlas exposes a Model Context Protocol (MCP) server so AI agents can run the entire signing lifecycle through tool calls. This is the defining Atlas workflow: a user tells their assistant “send this NDA to Alice for signature,” and the agent handles it end to end — agents prepare, humans approve.
The MCP surface speaks JSON-RPC 2.0, not REST. Because JSON-RPC is not described by OpenAPI, this surface is documented here by hand rather than in the generated API reference.

​
Why MCP

The MCP server turns signing into a small, carefully designed tool set with the properties agents need:
  • Review-first by default — the agent prepares an envelope and returns a review URL; a human clicks Send. (Trusted template sends may auto-send.)
  • Idempotent writes — a retried tool call cannot double-create or double-send. See Idempotency.
  • One-call sends — provide the document and the parties in a single call.
  • Upload sessions — when the agent’s host can’t transmit files, Atlas returns a short-lived upload link; the user drops the file there and the agent completes the session.

​
Endpoint & auth

EndpointPOST https://api-atlaswork.vercel.app/api/mcp
ProtocolJSON-RPC 2.0
AuthAPI key (bearer token or x-api-key)
The MCP server uses the same API keys as the REST API. The API-key boundary is enforced in middleware before any method runs.

Transport details

Request and response envelopes, error codes, and a working example.

Tool suite

The tools available today and the full signing tool set being built out.