Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Atelier

by marmikshahversion 0.2.0i★ –iRuns on your computer
Registry nameio.github.marmikshah/atelier

Install

Overview

Description from the maker (original English)

Offline, headless pixel-art editor: draw, animate, inspect, and export sprites and fonts.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "atelier": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/marmikshah/atelier:0.2.0"
      ]
    }
  }
}

Run this in your terminal

claude mcp add atelier -- docker run -i --rm ghcr.io/marmikshah/atelier:0.2.0

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "atelier": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/marmikshah/atelier:0.2.0"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "atelier": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/marmikshah/atelier:0.2.0"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account marmikshah, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32688 servers in this category
  • Published to the registry more recently than 66% of the other 32688 servers in this category
  • Basic checks equal to or better than 100% of the other 32688 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Atelier safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 19 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, 御府和田玉 在售作品查询

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Atelier is an offline, headless pixel-art editor for command-line tools and AI agents. Create layered sprites and animations, inspect pixels, and export PNGs, spritesheets, GIFs, APNGs, and TrueType pixel fonts. Documents stay local.

Use it directly from a shell, or connect an agent such as Claude Code or Codex through MCP (Model Context Protocol). Both interfaces expose the same editing tools; no graphical editor or running server is needed for CLI calls.

Drawn by an agent through Atelier's tools. Each is rebuilt byte for byte from the recipe beside it in CI.

A more complex design made by combining physics simulation with Atelier MCP using Opus 5.5.

The replay file is too large to include here. Download it from Google Drive if needed.

Showcase

Install

On macOS, Ubuntu, or any other Linux, paste this into a terminal:

curl -fsSL https://github.com/marmikshah/atelier/releases/latest/download/install.sh | sh

Ubuntu Desktop comes without curl; use wget instead:

wget -qO- https://github.com/marmikshah/atelier/releases/latest/download/install.sh | sh

It downloads Atelier for your machine, checks it, puts it in ~/.local/bin, and adds that to your PATH. If Claude Code or Codex is installed, it also connects Atelier to them: they get its drawing tools in every project and its guides for drawing sprites and scenes and reviewing art. Nothing else is needed, not even Rust.

Then start a new agent session and ask for something:

Use atelier to draw a 32×32 animated torch and save it as torch.gif.

Your art is kept in ~/.atelier. To keep a project's art inside the project instead, run atelier init in its folder before you start the agent.

  • Update: Run the install command again.
  • Installed Claude Code or Codex afterwards? Run atelier connect.
  • A specific version or folder, or no profile changes: Set ATELIER_VERSION, ATELIER_INSTALL_DIR, or ATELIER_NO_MODIFY_PATH=1; install.sh lists every option.

Uninstall

atelier uninstall

It lists what it will remove and asks before deleting anything: Atelier's registration in Claude Code and Codex, its skills, the PATH line it added, the atelier program, and the Linux background server if you set one up.

Your art in ~/.atelier is kept; add --documents to delete it as well. Folders set up with atelier init are never touched.

Other ways to run it

  • From the terminal. Every tool is one command: atelier call TOOL ' '. Your first sprite walks through creating, drawing, and saving an image.
  • In Cursor and other MCP clients. Install as above, then register the path command -v atelier prints as a stdio server with no arguments, and run atelier skills install --for cursor (or --dir PATH for another skills folder) for the drawing guides:
  {

"mcpServers": { "atelier": { "command": "/full/path/to/atelier" } } }

  • In Docker. A container image is published for MCP clients that can launch Docker.
  • As an HTTP server or background service. See Running Atelier.
Build from source

On other platforms, or to build it yourself, install Rust 1.98 or later, then:

cargo install --locked --git https://github.com/marmikshah/atelier atelier

atelier connect

atelier uninstall removes a build installed this way too, through cargo uninstall.

I want to…Start here
Make art from the terminalGetting started
Run a server, use Docker, or choose where art is storedRunning Atelier
Find a tool's argumentsatelier tools --markdown or atelier tools --schema NAME
Build from a checkout, understand the code, or work on the showcaseDevelopment guide
Report a bug or security issueIssues · Security

Stability

Atelier is at 0.2. master is the current source; releases are dispatched from it and publish the macOS and Linux binaries, the container image, a vX.Y.Z tag, and the MCP Registry entry.

  • Your documents are not discarded. Edits are journaled and committed atomically. A document that is damaged, or saved by a build with a different document schema, is refused with an error and left unchanged on disk.
  • The document format is versioned, with no migration. If an update changes it, documents saved before it are refused, stay on disk untouched, and open again with the commit that wrote them.
  • A recipe is the plain log of the calls that built a document, one JSON line each. It has no version of its own: what it draws depends on how the tools behave, so a recipe from one commit replays exactly on commits whose tools draw the same way.
  • Tool names and arguments can still change between commits. Pin a commit if you script against them, and read the current surface from atelier tools --markdown.

How it is built

100% of this code was written by AI. Atelier began as an experiment in whether agents, using only tool calls, can make art useful in games. My part has been giving direction, and I hope the result helps you make something of your own.

CI checks formatting, strict Clippy, and the Rust test suite on Linux and macOS, smoke-tests the container, and replays every showcase recipe, which must reproduce its GIF byte for byte. The security policy describes the network and file-access boundaries.

[!NOTE]

None of the code has had line-by-line human review. Bugs, security issues, and breaking changes are still possible. Please review the code and work with copies of important data before using it in production.

Contributing

Bug reports and questions are welcome as issues; include the checkout commit and a minimal command sequence or recipe file. Pull requests from outside the project are not accepted. Report vulnerabilities privately through the security policy.

License

MIT © Marmik Shah

Ask PopNx