Atelier

MCP server

@atelier/mcp is a Model Context Protocol server that exposes Atelier as native tools to any MCP-compatible AI agent. Claude Code, Codex CLI, OpenCode, Cursor, Windsurf, Cline — all of them call Atelier without custom integration.

Tell your agent “deploy this to atelier” and it happens. Tell it “show me the last 50 errors” and it pulls them. The agent doesn’t need a plugin per editor; it needs MCP.

Install

The server is a single npm package; nothing to install globally.

npx @atelier/mcp --version

Configure

Claude Code

// .mcp.json
{
  "mcpServers": {
    "atelier": {
      "command": "npx",
      "args": ["@atelier/mcp"],
      "env": { "ATELIER_TOKEN": "${ATELIER_TOKEN}" }
    }
  }
}

Codex CLI

# ~/.codex/config.toml
[mcp_servers.atelier]
command = "npx"
args = ["@atelier/mcp"]
env.ATELIER_TOKEN = "${ATELIER_TOKEN}"

OpenCode / Cursor / Windsurf

Use the editor’s MCP configuration with the same command + args pattern. See each editor’s docs for the exact file location.

Token

ATELIER_TOKEN comes from atelier login (stored in your OS keychain). The MCP server reads it from the env var or directly from the keychain — whichever you prefer.

Tools exposed

The agent sees these tools and calls them natively:

ToolPurpose
atelier.project.createCreate a new Atelier project
atelier.project.linkLink this directory to an existing project
atelier.db.queryRun a parameterized read query
atelier.db.migration.newWrite a new migration file
atelier.db.migration.applyApply pending migrations
atelier.db.schema.dumpGet current schema as SQL
atelier.storage.uploadUpload a file to a bucket
atelier.storage.listList files in a bucket
atelier.functions.invokeCall a Function with payload
atelier.functions.logsTail Function logs
atelier.deployDeploy current code (canary by default)
atelier.rollbackRoll back to previous deployment
atelier.deployments.listList recent deployments
atelier.logs.tailTail app logs
atelier.env.list / set / unsetManage environment variables
atelier.vector.searchVector similarity search
atelier.vector.embedEmbed via your BYOS provider

How it works

Cursor / Claude Code / Codex / OpenCode
        │ MCP tool call

@atelier/mcp (stdio)
        │ ConnectRPC over HTTPS

api.atelier.style


Base infrastructure

For tools that hit your LLM provider (e.g., vector.embed), the MCP server routes through the desktop tunnel so your BYOS tokens stay on-device — same privacy model as Studio.

Examples

“Migrate the database to add a priority int column on todos, default 0.”

Agent calls:

  1. atelier.db.migration.new with the SQL
  2. atelier.db.migration.apply to apply locally
  3. Asks for confirmation before atelier.db.push (production)

“Why is the live app failing?”

Agent calls:

  1. atelier.logs.tail with last 5 minutes
  2. atelier.deployments.list to find the bad deploy
  3. Proposes atelier.rollback

See also