Site listing and settings are table stakes for a hosting API; running `wp search-replace` on a live site from the same conversation is not, and it turns a migration chore into a sentence. That reach cuts both ways — the same tool runs arbitrary shell commands on your server, so it wants your client's approval prompt in front of it.
A Python server on the SiteBay WordPress hosting platform. It covers the full lifecycle of a hosted site — create it from a template, change its settings, run commands on the server, edit files in wp-content, delete it — without opening the control panel.
- `sitebay_list_sites` lists your hosted sites; `sitebay_get_site` returns one site's details including active state, HTTP auth and plan
- `sitebay_create_site` creates a WordPress site from a ready-made template; `sitebay_list_ready_made_sites` shows which templates exist
- `sitebay_update_site` changes Cloudflare settings, domain, HTTP auth and Git URL; `sitebay_delete_site` removes a site
- `sitebay_site_shell_command` runs shell or WP-CLI commands on the SiteBay server — `wp plugin list`, `wp search-replace`, `df -h`
- `sitebay_site_edit_file` edits files in the wp-content directory, such as a theme's style.css
A SiteBay API token: log in at `my.sitebay.org`, go to Settings → API Tokens, generate one, and pass it as `SITEBAY_API_TOKEN`. Run it as `uvx sitebay-mcp` over stdio, or `pip install sitebay-mcp`, or install through Smithery with `npx -y @smithery/cli install @sitebay/sitebay-mcp --client claude`. It can also run over HTTP — `uvx sitebay-mcp --http` binds 127.0.0.1:7823 by default, and `MCP_TRANSPORT`, `MCP_HTTP_HOST` and `MCP_HTTP_PORT` set the same thing from the environment. Tokens can be revoked from the dashboard at any time.
One command plus a key — uvx sitebay-mcp, then supply credentials