hostinger/api-mcp-server/wordpress
Claude Code and agent skill by hostinger/api-mcp-server
- community
Checking that the SKILL.md file is still in the repository.
Provision a headless WordPress backend for the Hostinger Headless flow: create the headless website with WordPress at /cms, verify and self-heal, then record it in site.json.
Install
npx vskill@latest install hostinger/api-mcp-server/wordpressSKILL.md
The same SKILL.md was published earlier as hostinger/api-mcp-server/wordpress.
headless-step-provision-wordpress
Create the headless WordPress backend for <domain> and prove it is ready. One platform call lays every headless site out identically: WordPress in public_html/cms, Hostinger AI Assistant + MCP adapter, site marked headless. Out: site.json.
All operations below go through the Hostinger connector (execute).
Fire vs join (background provision). Step 1, plus the queuing call —hosting_websites_createfor a fresh site (Step 2) orwordpress_installations_installto swap an empty headless shell(Step 2b) — are the fire half: once the job is queued, recordprovision.in_progressand returnto do prepare work (see the router../SKILL.md). The readiness poll at the end of Step 2 / 2b,plus Steps 3–6, are the join half — run them when an instance-barrier step needs the backend (orimmediately, if the agent can't interleave). An already-completedsite with WordPress at/cmsdetected in Step 1 means provision is already done: recordprovision.completedand adopt it.
Step 1 — Detect before you create (never provision twice)
hosting_websites_list { "domain": "<domain>" }— substring filter, so exact-match the row's
domain. If a row exists, note username, order_id, website_type.
- No exact row → nothing exists on this domain → create fresh (Step 2).
- A row exists. If
website_typeis notheadless, stop and tell the user — this domain
already hosts a different kind of site (plain WordPress, Node.js, builder, …); never overwrite it. If it is headless, work out whether WordPress is already installed or the shell is still empty: check hosting_websites_list-setups { "domain": "<domain>" } (exact row) and wordpress_installations_list { username, domain, ownership: "all" } (exact row):
- Setup
running→ provisioning is underway → skip to Step 2's poll. - Setup
failed→ tell the user and point them at hPanel; do not callhosting_websites_createagain yourself. - A WordPress install with
directory: "cms"already present (or setuptype: headless_wordpress)
→ already provisioned → skip to Step 3 (adopt it).
- A
headlesssite with no/cmsinstall (an empty headless shell — setup
type: headless_empty, typically from onboarding) → swap it to WordPress (Step 2b). Do not call hosting_websites_create again — the website already exists; you only install WordPress into it.
Step 2 — Create a fresh headless WordPress site (only when no site exists)
- Pick the plan:
hosting_orders_list { "statuses": ["active"] }. One active order → use it; several
→ ask the user which.
- Start the setup:
``json { "operation": "hosting_websites_create", "params": { "order_id": <order_id>, "type": "headless_wordpress", "domain": "<domain>" } } ``
domain must be a customer-owned domain. For a temporary *.hostingersite.com subdomain, omit `domain` — the setup generates one itself and returns it in the response. Don't call a separate subdomain op to make one first: there's no need in this flow. The response then carries the generated domain: if it differs from the workspace directory name, move ~/.hostinger/<old>/ to ~/.hostinger/<new>/ (if <new>/ already exists, stop and ask instead of moving into it), update the domain in brief.md, and tell the user the new domain. Admin credentials are generated by the platform; never ask the user for a password.
- Don't wait here. At the join,
cd "$HOME" && node <skill>/wait.mjs setup <domain>(see Waiting on Hostinger in
the top-level SKILL.md) returns once the setup is completed, usually at once by then. A failed setup → stop, point at hPanel.
Step 2b — Swap an empty headless shell to WordPress (only when onboarding already made the shell)
The website already exists as an empty headless shell, so there is no `hosting_websites_create` here — you install WordPress straight into its /cms directory. This is the onboarding handoff path.
- Use the shell's
usernameandorder_idfrom Step 1's row — no new order pick, no new website. - Install WordPress into
/cms, flagged headless:
``json { "operation": "wordpress_installations_install", "params": { "username": "<username>", "domain": "<domain>", "type": "headless", "site_title": "<the brief's Site name>", "credentials": { "login": "<admin login>", "email": "<account email>", "password": "<strong generated password>" } } } ``
type: "headless"installs into/cmswith the Hostinger headless MU plugin and marks the site
headless-WordPress; `directory` is not allowed with it (it is always cms). The target must already be headless — the headless install rewrites the root .htaccess, so the API rejects it with 422 on any non-headless site (which is why Step 1 confirms website_type: headless first).
- You generate the admin password (strong, 8–50 chars, mixed case + a digit) — never ask the user
for one and never print it. The user signs in later through a one-click login link (Step 6), so the password only has to exist, not be remembered.
- A new database is created for the install unless you pass
database.nameof an existing one; the
generated database counts against the plan's limit.
- The call is asynchronous — a success response only means the install job was queued. This is
the fire: record provision.in_progress and return to prepare work. At the join, cd "$HOME" && node <skill>/wait.mjs cms <domain> <username> returns the /cms install row (directory: "cms", valid) once it exists, usually within 1–2 minutes of the install.
Step 3 — Verify (all must pass)
| Check | How | Expect | |
|---|---|---|---|
| Site is headless | hosting_websites_list exact row | website_type: "headless" | |
WordPress at /cms | wordpress_installations_list { "username": "<username>", "ownership": "all" }, exact-match domain | row with directory: "cms", is_valid: true; note its id | |
| REST API answers | GET https://<domain>/cms/wp-json/wp/v2/posts?per_page=1 | 200, JSON array | |
| AI Assistant + MCP loaded | GET https://<domain>/cms/wp-json/ → namespaces | contains hostinger-ai-assistant/v1 and mcp | |
| JWT mintable | wordpress_installations_jwt-token { username, software: <id> } | returns token, mcp_url |
Notes:
wordpress_installations_listcan lag a few seconds behindcompletedand return[]— retry
briefly before failing. Its domain filter is a substring match, so exact-match the row.
- The install record's
urlmay sayhttp://; always usehttps://URLs. GET https://<domain>/returns 403 until the frontend is deployed — expected, not a failure.- A
jwt-tokenHTTP 500 can still have succeeded (a known quirk of thehostinger-wordpressMCP):
call it again before failing.
- Never print, log or store the JWT. It is minted on demand (24 h lifetime) by whichever stage
needs the per-site WP MCP; only mcp_url is recorded.
If a check fails: retry once after ~30 s; if it still fails, stop and point the user at hPanel.
Step 4 — Plugins (one install call for every plugin the site needs)
Install every wordpress.org plugin the site needs in one call, then poll once for all of them. This is join-half work (needs the live /cms install), so run it once provision.status == "completed". Build the slug list from the brief:
| Slug | Install when | If it doesn't come up | |
|---|---|---|---|
wordpress-seo (Yoast SEO) | Every site, unless the owner declines it when told (then record seo.enabled: false) | Record seo.enabled: false, tell the user in one line, and let the frontend generate tags from content | |
woocommerce | The brief's Suggested backend is **WordPress + WooCommerce** | Stop and point the user at hPanel: a store can't work without it | |
contact-form-7 | The brief's Must-haves include a contact form | Record contact_form.enabled: false, tell the user in one line, and let the frontend render the contact page without a form |
Yoast is on by default so per-page title/description/Open Graph/JSON-LD come from a maintained plugin's yoast_head_json rather than being hand-generated by the frontend. Tell the user in one line which plugins you're installing; drop wordpress-seo if they say they don't want SEO.
- Install all of them in one call (management MCP, async):
wordpress_plugins_install { username, software: <install_id>, plugins: [<every slug from the table>] }. An HTTP 500 doesn't mean it failed (a known quirk of the hostinger-wordpress MCP): go straight to the poll, and never send a second install blindly.
- Poll
wordpress_plugins_list-installed { username, software }until every slug showsactive
(install and activate usually complete together). Activate a slug that is installed but inactive with wordpress_plugins_activate { username, software, plugin: "<slug>" }.
- A slug that doesn't come up. The poll names it, so handle only that slug: if it is still not
active after about two minutes of polling, send one more install with only the slugs that aren't active, poll again, and apply each remaining slug's fallback from the table. Never fail provision over Yoast or Contact Form 7.
Step 5 — Per-plugin checks (each slug Step 4 left `active`)
A check that fails means that slug didn't come up: apply its fallback from Step 4.
- SEO (
wordpress-seo):GET https://<domain>/cms/wp-json/→namespacesonce more, and a sample
post/page response carries yoast_head_json. The per-item Yoast meta (focus title/description per post) is set later in the content-model push; provision only installs and activates the plugin.
- A store (
woocommerce): verify it and record it insite.jsonper
`../../04-content-model/wordpress/woocommerce.md` §0.
- A contact form (
contact-form-7): verify it and record it insite.jsonper
`../../04-content-model/wordpress/contact-form.md` §0.
Step 6 — Record site.json
No passwords or tokens in site.json. When the user needs wp-admin, mint a one-click link with wordpress_login_create-links { username, software: <install_id> } — never hand over a password.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/headless/steps/03-provision/wordpress/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/hostinger/api-mcp-server/wordpress)