Four Ways to Install the Apatero MCP, Compared

There are four ways to put Apatero inside Claude, and people keep asking which one is correct. The honest answer is that they all reach the same twenty tools. The right pick depends on your client, your runtime, and how much you enjoy terminals.

This post compares the hosted connector URL, the npx bridge, the uvx package, and the Homebrew tap. By the end you will know exactly which one to run, and what to do when a setup misbehaves.

The MCP install guide has all four with copyable snippets. This is the reasoning behind the choice.

Quick Answer: On claude.ai or the Claude mobile and desktop apps, paste the connector URL and you are done. In Claude Code, use npx if you have Node or uvx if you live in Python. Choose brew when you want a pinned, real install on macOS instead of an ephemeral runner.

The Four Paths at a Glance

Every path authenticates the same two ways. OAuth in the browser by default, or an ap_live_ API key from app.apatero.ai/developer when you need headless auth.

Path One, the Hosted Connector URL

The connector is the zero-install option. On claude.ai, open Settings, then Connectors, then Add custom connector, and paste the URL.

https://mcp.apatero.ai/mcp

Sign in with your Apatero account when prompted, and the tools appear in your next conversation. Because we host the server, there is nothing to update, ever. It is always the current version.

This is the correct path for anyone who does not want a terminal involved. It is also the only path available on the phone, which matters more than people expect. A surprising amount of influencer-pipeline babysitting happens from a couch.

The tradeoff is control. You cannot pin a version, and you cannot point it at custom tooling around your shell. For most people neither matters.

Path Two, npx and the Node Bridge

The apatero-mcp package on npm is a thin bridge that Claude launches on demand. If Node is on the machine, one command wires it into Claude Code.

claude mcp add apatero -- npx apatero-mcp

For Claude Desktop, the same bridge goes into claude_desktop_config.json with npx as the command. Restart the app after saving, since Desktop only reads config at launch.

The npx path is the default recommendation for developers. No Python, no environment management, and each launch resolves the latest published version, so updates are automatic. I wrote a full walkthrough of this path covering setup in both clients and the first generation from chat.

The tradeoff is cold starts. The first launch after a cache clear downloads the package, which adds a few seconds once. If that bothers you, brew exists.

Path Three, uvx From PyPI

Same server, Python packaging. The apatero-studio-mcp package on PyPI runs in one line through uvx, with no virtualenv to create and no requirements file to maintain.

claude mcp add apatero -- uvx apatero-studio-mcp

Choose this when uv is already your daily tool and Node is not installed. Data folks, ML tinkerers, and anyone whose dotfiles mention pyproject.toml will feel at home. Functionally it matches the npx bridge, including automatic version resolution on each launch.

If you have neither Node nor uv, installing a runtime just for this is the wrong move. Use the connector URL or brew instead.

Path Four, Homebrew

The tap ships a real binary for macOS.

brew install apatero-org/tap/apatero

Then register the installed binary with your client.

claude mcp add apatero -- apatero

Brew is for people who want the boring virtues. A pinned version that only changes when you run brew upgrade apatero, no runtime dependency at launch, and instant starts because nothing is fetched on demand.

It is the best choice for a machine you administer deliberately, and the worst choice for a machine where you never open a terminal. It is also macOS only, so Windows folks should look at npx or the connector.

Which Path for Which Client

On claude.ai in the browser, use the connector URL. There is no second option, and you do not need one.

In the Claude mobile apps, the connector again. Connectors added to your account travel with it.

In Claude Desktop, you have a real choice. The connector is simpler. The local bridge through npx gives you environment-level control, like setting APATERO_API_KEY for key auth. Pick the bridge if you know why you want it, and the connector if you do not.

In Claude Code, use npx with Node or uvx with Python, and brew if you want the pinned binary. All three register through the same claude mcp add pattern.

On a server or in CI, use npx or uvx with an API key in the environment. OAuth needs a browser, and your build runner does not have one.

The pattern underneath is the one that decides most tooling debates, hosted versus local. It is the same tradeoff I mapped in Apatero versus a custom ComfyUI stack, just at a much smaller scale. Hosted wins until you have a specific reason to hold the process yourself.

Troubleshooting Basics

Most broken setups are one of five problems.

Tools do not appear in Claude Desktop. You edited the config but did not restart the app. Quit it fully and relaunch, since the config is only read at startup. Check the JSON for a missing comma while you are there.

The npx launch fails. Your Node is ancient or npx cannot reach the registry. Update Node, then run npx apatero-mcp once in a terminal by itself and read the actual error, which is usually clearer outside the client.

uvx says command not found. uv is not installed or not on PATH. Install uv first, confirm uvx runs in a terminal, then re-add the server.

Auth keeps failing. If you use a key, confirm it starts with ap_live_ and that the environment variable is actually set for the client process, not just your shell. If you use OAuth, sign in again from the browser prompt. Keys can be rotated at app.apatero.ai/developer.

The server connects but calls error out. Check your credit balance from the chat, and check status inside Claude Code with the /mcp command. A connected server with failing generations is almost always an account-level issue, not an install issue.

Wrapping Up

All four paths end at the same place, twenty studio tools inside your Claude client. The connector URL is the default for claude.ai and the apps. npx is the developer default. uvx serves the Python crowd, and brew is there for people who like their binaries pinned and boring.

Install one today and make something. Signup takes a minute, and your first generation is free, which is exactly enough to feel the loop of asking for an image in chat and watching it land in your gallery.

Open Apatero, claim your free first generation →