← All posts

Claude Code needs SSH. You don’t need to know what that means.

As a web host, I’ve always kept a pretty clear line around what I do. Anything that affects the health of a website is mine. Uptime, backups, security, and the routine maintenance of keeping every plugin up to date.

Building websites was not. Fixing things on a website was not. Setting up a form, configuring a plugin, changing content on a page. That was the web designer’s job, and I stayed out of it.

That line doesn’t make sense anymore.

With Claude Code I can do almost all of it, almost effortlessly. I can build sites. I can set up forms. I can configure plugins. Everything that would be categorized as the web designer’s responsibility, I can now do as a web host.

And I can do it faster than the agency can. Not because I’m a better designer. Because I’m using Claude Code and they aren’t.

That’s not a knock on agencies. It’s the opposite. I want the people building sites on Anchor Hosting moving at the same speed I am. So this post is for the agency owner, the web designer and the web developer. Here’s how to connect Claude Code directly to your Anchor Hosting account and let it drive.

Claude Code needs SSH. You don’t need to know what that means.

I think this is the real reason more web designers aren’t driving Claude Code for their WordPress work. The moment it comes up, the conversation turns into SFTP, SSH, keys, ports and terminals. Plenty of really talented designers have never needed any of that, and it feels like a wall.

Here’s the thing. You don’t need to know it.

You just need to know that Claude Code needs a way into the server in order to drive itself. With that access it can run WP-CLI, read the files, query the database and check its own work. Without it, Claude is guessing, and you’re the one copying and pasting between a chat window and wp-admin.

So I built that door into Anchor Hosting. You sign in, click Allow, and Claude Code has the access it needs. No keys to generate. No SFTP client. No hostname or port to look up.

Claude Code asks to add a contact form on example.com. The request passes through the Anchor Hosting Claude connector, signed in as you, which handles SSH keys, SFTP and ports. WP-CLI commands and an API call run on the production site, and each one is written to the activity log.
You ask in plain words. Claude works through the connector as you, and every change lands in your activity log.

Setting it up takes about a minute.

Open your Profile in the Anchor Hosting dashboard. There's a Claude connector card with everything you need. In a terminal, run this:

claude mcp add --transport http anchor-hosting https://anchor.host/wp-json/captaincore/v1/mcp

Then start Claude Code and type /mcp. Pick anchor-hosting and choose Authenticate. Your browser opens to an Anchor Hosting sign in page. Sign in, read what Claude is asking for, and click Allow.

That's it. Claude Code can now see every site you manage with us.

Not a terminal person? The same connector works in Claude on the web, the desktop app and your phone. In Claude, open Customize → Connectors → Add custom connector and paste the URL from the Claude connector card.

What clicking Allow gives Claude
SEE
The sites you manage
The same list you see in the dashboard. A customer sees their own sites. An agency login sees its whole roster. Nothing else.
RUN
WP-CLI and shell commands, as you
Content, plugins and settings, on production or staging. It's the SSH access Claude needs, without you ever touching SSH.
DASHBOARD
Everything else the dashboard does
New sites, backups, domains, DNS, staging deploys, PHP and cache, invites, support chat. Claude looks up the right API call and makes it as you.
LOG
Every command is recorded
Each command Claude runs, and every change it makes, lands in your account's activity log.
REVOKE
Disconnect any time
Each connection shows up under Profile → Application passwords. Revoke it and Claude is out. That password only works for the connector, so it can't be reused anywhere else.

Then you just describe what you want.

Once it's connected, you stop thinking in terms of hosting panels and plugin settings screens. You describe the outcome. Content changes, new forms, new pages, plugin configuration, even a brand new site. It's all just a few words away.

Here's the kind of request I mean.

Example Claude Code Session
Austin
On customer-1-fake.com, add a contact form to the Contact page. Name, email, phone, and a dropdown for which service they need. Send entries to the office address.
Claude
Found customer-1-fake.com. Gravity Forms is installed and active on production. I'll check the Contact page first, then build the form and place it below the intro paragraph.
Claude
Done. The form has your four fields plus a notification to the office address. I submitted a test entry and it arrived. Here is the page to review.
Austin
Looks good. Now do the same on the staging copy of customer-2-fake.com, but use their brand colors on the button.

No one in that exchange had to know where the site lives, what PHP version it runs or how to connect to it. Claude worked that out from the access it was given.

There's more than one way in.

The connector is where I'd start. It's not the only option though, and it's worth knowing what the others are.

Ways Claude can reach your sites on Anchor Hosting
Way inSetupWhat Claude can doBest for
Claude connectorSign in and click AllowEverything the dashboard does, plus WP-CLI and shell commands on production or staging. Every change loggedMost agencies
Application password + API docsCreate a password in Profile and hand Claude the API docsEverything the dashboard does, over the REST APIAutomations and your own tools
Your own SSH keysAdd a public key in Profile. Kinsta sites use the SFTP password on each siteAnything the server allows, outside the activity logPeople who already live in a terminal

I use Claude Code like it has root access. You probably shouldn't.

Full disclosure. My own setup is the far end of that table. Claude Code drives CaptainCore directly for me, with access to the whole fleet. I built the platform, I'm watching it all day, and it makes sense for how I work.

It probably doesn't make sense for most people running an agency.

The connector is a narrower door on purpose. It only sees your sites. Every command is written down. It can't touch your passwords, your two-factor settings or your payment details. It can be shut off with one click. And it tells Claude how to behave when it connects: read the current state before changing anything, prefer changes WordPress can undo, confirm before anything destructive, and use staging when you want to try something safely.

Claude acts as you
Anything you could break in wp-admin, Claude can break too. Try new things on staging first, and skim the activity log for the first few weeks so you get a feel for what it's doing.

The bigger shift is learning to move at the speed of an agent.

Connecting Claude Code to your hosting is the easy part. The harder part is changing how you work.

For a lot of creative professionals, AI is still a side tool. Something you ask for copy ideas or a code snippet, then go back to clicking through wp-admin yourself. That's leaving almost all of it on the table.

The agent should be the primary way the work gets done. You decide what the site needs. Claude does the clicking, the configuring and the checking.

That's the gap I want to help close. Not everyone is going to run Claude Code with the keys to everything, and they shouldn't have to. They just need a safe way to hand it the access it needs.

Now there is one.

Austin Ginder
Subscribe