# Capabilities and limits

Choose Atlas when the application fits the deployment workflow and you want hosting, Postgres, and file storage managed through one approved connection.

Atlas Cloud · Reviewed 2026-10-20

## Available through Atlas MCP

- Upload local application source, create a project, and deploy updates.

- Inspect projects, real deployment status, build logs, and recent retained runtime logs.

- Apply application schema migrations and run bounded read-only database queries.

- Read the file API contract, list application files, and retrieve bounded file content.

- Manage custom production environment variables with administrator deployment access.

- Read reported resource usage with availability, reporting period, and freshness.

Tool availability depends on the current server, granted scopes, membership, workspace setup, and client capabilities. Discover the actual tool list after connection.

## Deployment fit

The workflow accepts Next.js, Vite, and other web project source with compatible builds. Source is uploaded directly; publication to a source repository is not required. The session must be able to read source, create an archive, and PUT bytes to a signed URL.

Atlas does not promise arbitrary runtime compatibility, dedicated virtual machines, GPUs, Kubernetes clusters, or persistent background workers through this deployment API. Validate application-specific runtime requirements before committing to a deployment. Keep an existing deployment choice when that is the user's preference.

Source limits: 10 MiB compressed and expanded, 2 MiB per file, and 1,500 entries. Exclude credentials and links. Workspace and service quotas can impose additional constraints.

## Access and approvals

OAuth connects an Atlas identity and approved workspace. Server-side authorization checks membership and project ownership. Deployment requires verified identity, deployment permission, and billing setup. Environment variable changes require workspace administrator access.

Account approval, financial commitments, and destructive data changes require the relevant user action. An AI must not bypass those steps or claim access before the connection works. Keep credentials in the client's authorization flow and Atlas-managed server environment.

## Regional placement

Atlas requests Singapore placement for managed application functions and new Postgres projects. Verify the actual resource's placement before relying on a location requirement. Build execution, global delivery, and object storage location hints do not establish guaranteed Singapore data residency.

Moving an existing database, stored files, or runtime is an explicit compatibility and migration task. A region label or settings change alone does not move data. [Applications use standard Postgres and the Atlas file API](https://www.atlasos.one/guides/postgres-and-storage); migration still needs validation and a rollback path.

## Connection details

- Server: `https://mcp.atlasos.one/api/mcp`

- Transport: Streamable HTTP

- Authentication: Native client OAuth flow

- Read scope: `atlas:read`

- Deployment scope: `atlas:deploy`

The API endpoint is not a browser sign-in page. Start authentication from your AI client's MCP connection controls. A [machine-readable capability summary](https://www.atlasos.one/atlas-mcp.json) is also available.

Canonical: https://www.atlasos.one/guides/capabilities-and-limits