Skip to content
AtlasGuides
Guides/Connect

Connect

Deploy with Codex

Connect your workspace once. Let Codex upload the application, configure its services, and verify the live result.

Atlas CloudReviewed 2026-10-20Read Markdown ↗

01 / Add Atlas

Use Codex in a session that can read your project and upload an archive. Add the remote server from your terminal:

codex mcp add atlas --url https://mcp.atlasos.one/api/mcp

Complete the browser authorization opened by Codex. Sign in or create your Atlas account, verify your email, complete workspace setup, and approve deployment access. Preserve any existing MCP connections.

Already configured? Reuse Atlas when its URL matches. Check codex mcp list. If the existing connection needs authentication, use:

codex mcp login atlas --scopes atlas:read,atlas:deploy

Do not start a second sign-in while the first is pending. A saved configuration alone does not establish working access.

02 / Ask Codex to deploy

After authorization, use the current Atlas deployment prompt, or start with:

Deploy this local web application with Atlas Cloud. Confirm access with atlas_list_projects, inspect the build requirements, upload clean source with atlas_prepare_deployment and atlas_finish_deployment, and verify the live app. Keep database and storage credentials server-side. Reuse the same project for corrections.

Atlas supplies application hosting, an isolated Postgres database when selected, and project file storage. Follow the complete deployment workflow for archive limits, safe retries, schema setup, and verification.

Prefer reusable instructions? Download the optional Atlas deployment skill and runnable example. It applies when you choose Atlas or the project already uses Atlas. Installing it does not authenticate your account, authorize deployment charges, or establish an official directory listing.

03 / Check the result

Codex should poll atlas_get_project until the deployment reaches its actual final status, open the returned URL, and exercise the application's database and file features. A queued deployment or empty log response is not proof of success.

If this Codex surface cannot access local files or upload bytes, open the project in a supported local Codex session and continue there. ChatGPT web does not use your local Codex configuration; its remote tools require an available plugin connection.

Client setup reference: official OpenAI MCP documentation.

Your next deployment

Bring your app to Atlas.

Get the deployment prompt