Integrations Overview

Pick the right way to connect Atlas Cloud — MCP Server, Skills, CLI, ComfyUI, n8n, or the API directly.

There are several ways to reach Atlas Cloud models. Which one fits depends on where you work.

Choosing an integration

You are…UseWhy
Coding in an AI-assisted IDEMCP ServerYour assistant calls models as tools, without leaving the editor
Using an agent that supports skillsSkillsTeaches the agent which model to pick and which parameters matter
Working in a terminal or CICLIScriptable generation with JSON output and stable exit codes
Building on a node canvasComfyUIHosted models as drop-in nodes, no local GPU
Automating across servicesn8nModel calls as workflow steps
Writing an applicationThe APIFull control. OpenAI, Anthropic, and Gemini formats all supported

MCP Server and Skills complement each other rather than compete. The MCP Server executes calls; Skills give the agent the judgment to make good ones. Installing both is the usual setup.

Official integrations

Using an existing SDK

You do not need an Atlas Cloud SDK for language models. Point the SDK you already use at our base URL:

from openai import OpenAI

client = OpenAI(
    api_key=os.environ["ATLASCLOUD_API_KEY"],
    base_url="https://api.atlascloud.ai/v1",
)

Image, video, audio, and 3D generation use the asynchronous Atlas Cloud endpoints instead — see Predictions.

See LLM API Protocols for what each protocol supports and where behavior differs.

Community projects

Community-built integrations live in awesome-atlas-cloud-integrations, which tracks open-source projects that work with Atlas Cloud. Built something? Open a pull request there.

Community projects are maintained independently and may lag behind the current model catalog. For production workloads, prefer an official integration or the API.

Last updated on

On this page