> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlaswork.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP transport

> Connect an MCP client to Atlas's hosted Streamable HTTP server.

Atlas MCP is hosted by Manufact at:

`https://mcp.atlaswork.ai/mcp`

Clients should connect with their native remote-MCP flow. Do not handcraft
JSON-RPC requests or enter an Atlas API key: the host negotiates the MCP
Streamable HTTP session and starts Atlas OAuth automatically.

## Connection flow

1. The client initializes a Streamable HTTP MCP session.
2. The server challenges unauthenticated requests and publishes protected
   resource metadata.
3. The client dynamically registers with Atlas OAuth.
4. The user signs in, approves the requested scopes, and returns through PKCE.
5. The client lists and calls the typed Atlas tools.

Scopes are limited to the tool surface:

* `envelopes:read`
* `envelopes:write`
* `documents:write`
* `extract:read`
* `offline_access`

## Tool results and errors

Successful tools return concise structured content. Supported clients also
render the `atlas-result` MCP App for envelope progress, templates, extraction,
review links, document uploads, and status refresh.

Validation and Atlas API failures are returned as actionable MCP tool errors.
Authentication failures remain protocol-level OAuth challenges. Atlas assigns
an `X-Request-Id` to each upstream API call so operators can correlate Manufact
and Atlas logs without recording access tokens or contract contents.

## Direct REST integrations

Backend integrations that do not use an MCP client should call
`https://api.atlaswork.ai/api/v1` with an Atlas API key. See the
[authentication guide](/guides/authentication).