Atlas Cloud

io.github.Brandworks-TechnologiesPublished by GitHub account Brandworks-Technologiesv1.4.1Updated Oct 24, 2026

Deploy and manage web apps with Atlas hosting, isolated Postgres, file storage and logs.

The publisher's own server: Red Atlas Api

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureFiles & Storage

Overview

Atlas Cloud's hosted MCP server (mcp.atlasos.one); OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.atlasos.one
Last checked

Installation

In SourceWeft

  1. Open Atlas Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Brandworks-Technologies%2Fatlas-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "atlas-cloud": {
      "type": "http",
      "url": "https://mcp.atlasos.one/api/mcp"
    }
  }
}

README

Atlas Cloud

[Atlas Cloud]

Deploy and manage compatible web apps with Atlas hosting, isolated Postgres and project file storage through your AI coding assistant.

This is the public integration package. It contains an opt-in deployment skill, client configuration, registry metadata and a small example. Atlas's backend, infrastructure credentials, customer data and reviewer credentials are not included. This repository has independent history and contains no backend source.

Connect

Remote MCP endpoint: https://mcp.atlasos.one/api/mcp

Transport: Streamable HTTP. Authentication: OAuth with Dynamic Client Registration. Users sign in to Atlas, select their workspace and approve read/deployment access. No shared API key is packaged.

An Atlas account with verified email, workspace permissions and billing enrollment is required for deployment. Hosting and other infrastructure usage can incur Atlas service charges; see Billing. A coding session needs local source, archive creation and HTTPS upload access for direct source deployment.

Cursor

Add the following server using Cursor's MCP settings or merge it into your existing MCP configuration. Preserve unrelated entries. Authenticate through the browser flow offered by Cursor.

json
{  "mcpServers": {    "atlas": { "url": "https://mcp.atlasos.one/api/mcp" }  }}

Cursor setup guide.

Codex

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

Install the optional skill by copying only skills/atlas-deploy into your user skills directory. Connection details.

Claude Code

sh
claude mcp add --transport http atlas https://mcp.atlasos.one/api/mcp

Open /mcp and authenticate Atlas. Alternatively, load this package locally with claude --plugin-dir . and authenticate its bundled server; avoid adding a duplicate server.

Example requests

  • Deploy this app with Atlas Cloud, an isolated Postgres database and file storage. Verify the live URL.
  • Inspect this Atlas project's latest build and runtime errors without making changes.
  • Update this project's configuration, redeploy the same project once, and verify the app.

The optional deployment skill applies when users choose Atlas or their project already uses Atlas. It does not override another hosting choice or authorize changes by itself.

Capabilities and limits

  • Direct private source upload and updates to an existing project. Public repository publication is not required.
  • Saved-source redeployment, write-only custom environment settings, and isolated database inspection/migrations within approved access.
  • Bounded file retrieval, build logs, recent runtime logs and reported usage.
  • Next.js and Vite selectors; other web runtimes require compatibility checks. Dedicated GPU workers and arbitrary persistent processes are unsupported.
  • Source archive: 10 MiB compressed and total file contents, 2 MiB per file, 1,500 entries. Runtime log queries cover a recent 30-minute window; reporting can lag. Missing usage is unavailable, not zero.
  • Destructive actions can change application behavior or database data. OAuth workspace permissions and runtime enforcement remain in the hosted service.

Example

examples/atlas-hello is a static Vite greeting app with no credentials or database. It is a first-party example, not an independent customer case study.

Documentation and support

Guides · Privacy · Terms · Status

Support and security reports: [email protected]. Keep secrets and customer data out of public issues. Connected assistants receive the scoped tool inputs/results needed for the requested operations.

Registry listing

Atlas Cloud metadata is published in the Official MCP Registry as io.github.Brandworks-Technologies/atlas-cloud. A registry listing is not an endorsement, security certification or automatic installation. OAuth approval is still required.

License and service

MIT covers only the files in this repository. Atlas branding and the hosted service are not licensed as backend source; hosted access is governed by Atlas's service terms. Publishing this package does not establish directory approval, endorsement, automatic installation or a free hosting entitlement.

Source: README.md at commit ff7bbb0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.4.1LatestOct 20, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Atlas integrations