OPTIONAL / LOCAL INSTALLATION

Bring Atlas to your coding session.

Install the deployment instructions, connect your approved workspace, and ask your AI to verify the live result.

The package is maintained by Atlas. It has not been submitted to or approved by the official OpenAI or Claude directories. Installation is optional and does not grant account access or authorize deployment charges.

Review and download

Version 1.0.2 · Reviewed 20 October 2026. Each archive contains only the integration or example named below, with no private Atlas application source or credentials.

Deployment skill ZIP — instructions and references, without automatic MCP configuration.
Plugin ZIP — skill, portable OpenAI manifest, Codex and Claude Code compatibility manifests, and an OAuth MCP connection.
Local Claude marketplace ZIP — a local marketplace containing the same plugin.
Atlas hello example ZIP — a static Vite application for a first deployment.

Check the download against SHA-256 checksums or the release manifest. Extract and read the skill before installing. No install script or lifecycle hook runs from these packages. Read the Privacy Policy and Terms of Service. Publisher verification and directory review remain required before official listing.

Use the skill in Codex

Download and extract the deployment skill ZIP. Copy its atlas-deploy folder into your user skills directory, ~/.agents/skills/ (Windows: %USERPROFILE%\.agents\skills\). Review an existing folder before replacing it.
Start a fresh Codex session and invoke $atlas-deploy.
Reuse a matching Atlas connection. If none exists, add and authenticate it with the commands below.

codex mcp add atlas --url https://mcp.atlasos.one/api/mcp
codex mcp login atlas --scopes atlas:read,atlas:deploy

Complete the client’s browser authorization. Sign in to Atlas, verify your account, choose your workspace and approve the requested scope. For inspection alone, request atlas:read. Check codex mcp list and confirm access with atlas_list_projects. Read the Codex connection guide.

Use it in Claude Code

For a persistent local plugin installation, extract the local Claude marketplace ZIP, then run these inside Claude Code from its parent folder:

/plugin marketplace add ./atlas-cloud-marketplace
/plugin install atlas-cloud@atlas-cloud

Choose your preferred install scope and inspect what the plugin adds. Open /mcp, select its Atlas server and Authenticate. Invoke /atlas-cloud:atlas-deploy. Keep an existing standalone Atlas connection disabled while using the plugin connection to avoid duplicates.

For a one-session trial, extract the plugin ZIP and start claude --plugin-dir ./atlas-cloud. For instructions alone, copy the deployment skill into ~/.claude/skills/atlas-deploy and add the connection using the Claude Code guide. Local installation does not add Atlas to the official marketplace or configure your Claude web account.

Try a small deployment

The Atlas hello example is a first-party walkthrough. Its static greeting form uses no database, file storage or credentials. The source has been built and checked locally; this download does not claim a hosted deployment or an independent customer success story.

cd atlas-hello
npm ci
npm run build
npm run preview

Open the preview URL and test the greeting form, then ask your connected coding assistant:

Deploy atlas-hello with Atlas Cloud, framework vite and database false. Upload clean source directly. Poll the actual project to Ready, open its returned live URL, submit the form with Reviewer and report the real result.

Source deployment needs a local session with file access, archive creation and HTTP upload. Atlas requires verified account access, workspace deployment permission and billing setup. Deployment can incur Atlas service charges; there is no example price estimate. Follow the complete deployment guide for packaging limits and safe retries.

Keep access in your control

The skill applies when you choose Atlas or your project already uses Atlas. It preserves your other service choices. OAuth is completed in the client’s own flow; never paste tokens, passwords or callback URLs into a chat. Installing the skill does not authenticate the connection. Application database and file credentials stay server-side. Actual payable totals appear in Atlas Billing.

For current client behavior, see OpenAI MCP documentation and Claude Code plugin documentation. Need help? Contact Atlas.