If you spend your day in Claude Code or Codex, WordPress is the thing you have to leave the terminal for. You switch to a browser, log into wp-admin, click through four screens, and come back. It breaks the rhythm of everything else you do.
It does not have to. Vibery exposes every action it can take as MCP tools, so your assistant works on your WordPress sites the same way it works on your code.
What is MCP and why does it matter here?
MCP, the Model Context Protocol, is a standard way for an AI client to discover and call tools on a server. The value is that it is not Claude-specific. A single MCP endpoint works for every client that speaks the protocol.
For you, that means you are not betting on one assistant. Claude Code and Claude Desktop sign in with OAuth; Codex and your own scripts use an access token against the same endpoint.
Connecting Claude Code
One command:
claude mcp add --transport http vibery https://site-manager-api.sites.vibery.app/mcp
Claude registers the server and starts a sign-in with the same email link you use for the console. Approve it, and the connection reports back something like "Connected, 42 tools available".
From there, start by asking your assistant to list your sites. If it can see them, everything else works.
What can I actually ask for?
The useful mental model is that anything you would have done in wp-admin is now a sentence. In a single session you might:
- Deploy a template as a new site and get the URL back
- Draft and publish a post, with the SEO score checked if Rank Math is installed
- Import a product catalogue from a CSV on your own disk
- Create a rule that backs the site up nightly at 03:00
The last one is worth noticing. Because your assistant has access to your local files and to your sites at the same time, the import that used to mean "upload the CSV somewhere, then configure an importer" is just a path.
Do I have to use an assistant?
No. The console does everything the tools do. The agent is a faster front door, not the only one.
How do I keep this safe?
Access is a token you control, scoped to your tenant. Your token only ever sees your sites, and you revoke it in one click.
Nothing runs unattended, either. Your assistant proposes an action and you approve it. There is no background process making changes to a client site while you sleep.
No comments yet