This is the step that changes everything — and it's the one most beginners miss.

You just created accounts. But Claude Code can do far more than tell you to click around those websites: it can operate them for you. Each service has a command-line tool and an access key (an API token). Once Claude Code has the keys, things like "create a new GitHub repo, spin up a Vercel project, and add a Supabase database for it" become a single sentence you type — the agent does the whole thing, no web dashboards required.

Think of it as giving your assistant a key to each room. Do it once and you rarely touch those websites again.

The easy way: let Claude Code set it up

You don't have to memorize install commands. In the same terminal where claude runs, start Claude Code and paste this:

Please install the GitHub (gh), Vercel, Supabase, and Railway command-line tools in this
environment, then walk me through logging into each one. When a tool needs an access token,
tell me exactly where to create it and where to paste it.

Claude Code knows the right install steps for your system and will pause to let you log in. For most tools the login just opens a browser (or prints a link to open on your laptop). When a tool wants a token instead, here's where to generate one:

Service	Where to create a token
GitHub	Settings → Developer settings → Personal access tokens → Fine-grained tokens
Vercel	Account Settings → Tokens
Supabase	Account → Access Tokens
Railway	Account Settings → Tokens

Copy the token it shows you (you usually only see it once), and paste it where Claude Code asks.

What "injecting the key" actually means

Pasting a token during a CLI login is the simplest path — the tool quietly stores it for you. For keys an app needs while it runs (like the Supabase service_role key from the last step), Claude Code puts them in a hidden .env file in your project, which it reads automatically.

Treat every token like a password. They grant real access to your accounts. Keep them on your machine, let Claude Code place them in .env files (never paste them into a chat or commit them to GitHub), and if one ever leaks, delete it from that service's dashboard and make a new one.

Try it

Once a couple of tools are connected, test the payoff. Ask Claude Code:

Create a new private GitHub repo called hello-stack and confirm it exists.

If a fresh repo appears on GitHub without you opening the site — you've just turned your accounts into tools. That's the whole game from here.

Let's get you set up to build.

I'm on Windows

I'm on Linux / Mac