Agent skill

Migrate To Hosting

by hostinger in hostinger/api-mcp-server

Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an…

MITAuto-check passedDatabases

Install Migrate To Hosting

skills CLI
$ npx skills add hostinger/api-mcp-server --skill migrate-to-hosting -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hostinger/api-mcp-server migrate-to-hosting --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hostinger/api-mcp-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/migrate-to-hosting .claude/skills/migrate-to-hosting && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
migrate-to-hosting
GitHub stars
159
Token cost
~1.8k tokens
SKILL.md length
826 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an…

  • Works in 6 steps: What is being moved → Create the website on the real domain → Import → …
  • Tasks that involve SQL
  • SKILL.md covers Calling the operations, 1. What is being moved, 2. Create the website on the… and 3. Import, plus 3 more sections
  • Calls curl and mysql; reaches api.ipify.org

What it does

Migrate To Hosting is an agent skill from hostinger/api-mcp-server. Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an archive, Node.js apps from source. Creates the website on the real domain, imports files and database, tests the copy before any DNS change, then switches the domain and SSL. Triggers: migrate my site to Hostinger, move my website from another host, transfer my WordPress site, import my website, switch hosting to…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering SQL. It works with WordPress, PHP, SQL and Node.js. The licence is MIT.

When your agent uses it

  • Tasks that involve SQL

Example prompts

  • “/migrate-to-hosting”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. What is being moved
  2. Create the website on the real domain
  3. Import
  4. Test before DNS moves
  5. Switch DNS and SSL
  6. After the switch

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad9b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • mysql

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.ipify.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Migrate To Hosting loads about 1.8k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 826 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~136
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hostinger/api-mcp-server at commit 9cad9b4, republished under its MIT licence (© hostinger). 826 words, ~1,805 tokens.

Download SKILL.mdSave it as .claude/skills/migrate-to-hosting/SKILL.md (or your agent's skills folder).
name
migrate-to-hosting
description
Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an archive, Node.js apps from source. Creates the website on the real domain, imports files and database, tests the copy before any DNS change, then switches the domain and SSL. Triggers: migrate my site to Hostinger, move my website from another host, transfer my WordPress site, import my website, switch hosting to Hostinger.

Migrate to hosting

The old host keeps serving the site until the copy on Hostinger is proven to work. DNS moves last.

Calling the operations

  • Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "import wordpress").
  • Batch reads with multi-execute. Batches chain operations from one server only — the Hostinger Connector runs hosting, wordpress, agency-hosting, domains and dns as separate servers.
  • Imports and deploys overwrite the target website's contents; confirm the target before each one.

1. What is being moved

Establish, asking only for what cannot be inferred:

  • Site type: WordPress, static, PHP (with or without MySQL), or Node.js.
  • The export:
    • WordPress — an archive of the whole WordPress root (including wp-content and wp-config.php) and a .sql dump.
    • PHP — a files archive, plus a .sql dump when the app has a database.
    • Static — the files. Node.js — the source or its Git repository.
    • Without one, the user exports it from the old host's panel, or over SSH: tar -czf site.tar.gz -C /path/to/site . and mysqldump --single-transaction -u USER -p DBNAME > db.sql.
  • The exact home URL (https, with or without www) — WordPress keeps it in the database, so the new site must answer on the same one.
  • Current DNS, to preserve what already works:
bash
dig +short NS DOMAIN; dig +short A DOMAIN; dig +short MX DOMAIN; dig +short TXT DOMAIN
  • Cron jobs on the old host — they do not move with the files.

2. Create the website on the real domain

Create the Hostinger website on the domain being migrated, not on a free subdomain: step 4 tests it by pointing only this machine at Hostinger, so nothing changes for visitors yet.

  • Shared and Cloud: hosting_domains_verify-ownership first. When is_accessible is false, the user adds the returned TXT record at their current DNS provider, next to the existing ones, and verification is repeated. Then hosting_websites_create with domain and order_id (from hosting_orders_list), and poll hosting_websites_list-setups with domain every 10–15 s until status: completed.
  • Agency: agency-hosting_website-setups_create with the domain, flavor: "php-fpm", a settings.php.version matching the old host (options in agency-hosting_php_list-versions-for-order) and datacenter_code from agency-hosting_datacenters_list. Poll agency-hosting_website-setups_status until completed for the website_uid.

3. Import

hosting_import-wordpress-website, hosting_deploy-static-website and agency-hosting_deploy-php-application read files from this machine and exist only in the local hostinger-api-mcp server. On the hosted server (mcp.hostinger.com), upload the files first as described in the deploy-to-hosting skill ("Without the local deploy operations") and use the operation named in brackets below.

WordPress, Shared and Cloud: hosting_import-wordpress-website with domain, archivePath and databaseDump uploads both, extracts the files and imports the database; large sites take several minutes. [Upload site.zip and dump.sql, then wordpress_installations_import-website with archive_path and sql_path.] Then wordpress_installations_detect with username and poll wordpress_installations_list with domain until the install appears with is_valid: true.

Static, or PHP without a database: hosting_deploy-static-website [upload, then hosting_websites_deploy-static-site-archive]; Agency: agency-hosting_deploy-php-application [upload to .h5g/, then agency-hosting_files_import-website-from-archive].

PHP with a database, Shared and Cloud:

  1. hosting_databases_create with a strong generated password; read the full name, user and host back from hosting_databases_list.
  2. Import the dump from this machine: allow only its public IP (curl -s https://api.ipify.org) with hosting_databases_create-remote-connection, run mysql -h HOST -u USER -p NAME < db.sql, then remove the rule with hosting_databases_delete-remote-connection. Without a MySQL client, use hosting_databases_phpmyadmin-link and import there.
  3. Put the new name, user and password into the app's config file, with host localhost, before archiving; then deploy as above. Never ship the srvNNNN.hstgr.io host inside the app.
Show full SKILL.md (271 more words)Show less

Node.js: deploy with the deploy-to-hosting skill. When a dump must be imported, create the database with hosting_databases_create rather than hosting_databases_setup-website — the latter never reveals the password needed for the import — and pass the credentials through environment variables.

Agency: files with agency-hosting_deploy-php-application [or upload plus agency-hosting_files_import-website-from-archive]; the database with agency-hosting_databases_create-website, imported through phpMyAdmin in hPanel (no import operation exists). For WordPress, set the new credentials in wp-config.php before archiving.

4. Test before DNS moves

Find the server address: details.ipv4 for Agency; for Shared and Cloud, the A record for @ in the Hostinger zone (dns_records_list on the domain) or the IP hPanel shows for the website. Then point only this machine at it:

bash
curl -sSk --resolve DOMAIN:443:IP -o /dev/null -w "%{http_code}\n" https://DOMAIN/
curl -sSk --resolve DOMAIN:443:IP https://DOMAIN/ | grep -o "TEXT FROM THE LIVE SITE"
curl -sSk --resolve DOMAIN:443:IP -o /dev/null -w "%{http_code}\n" https://DOMAIN/wp-login.php

-k is expected here: the certificate for the domain can only be issued after DNS moves. Check the home page, an inner page and, for WordPress, the login page. For a look in the browser, the user adds IP DOMAIN www.DOMAIN to their hosts file and removes it afterwards. Fix anything broken now, while visitors still see the old site.

5. Switch DNS and SSL

Follow the connect-domain skill from its DNS step: keep every MX and TXT record from step 1, then install SSL once the domain resolves to Hostinger. When the user controls the old DNS, lowering the TTL of the A records to 300 a day ahead shortens the switch.

6. After the switch

  • Verify without --resolve: curl -sSI https://DOMAIN/ shows platform: hostinger.
  • Recreate the old host's cron jobs with hosting_cron-jobs_create (Agency: agency-hosting_cron-jobs_create-website).
  • Keep the old hosting running for a few days — some resolvers still cache the old address, and email hosted there must be moved separately.

© hostinger, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/migrate-to-hosting of hostinger/api-mcp-server.

Open the folder on GitHubat commit 9cad9b4

Compare with similar skills

Migrate To Hosting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Migrate To Hosting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Migrate To Hosting this skillhostinger/api-mcp-server159—~1.8kAutomated safety check: PassMIT
Ravendbravendb/docs115—~2.3kAutomated safety check: PassMIT
Php SQL Audit0xShe/PHP-Code-Audit-Skill4021 repos~668Automated safety check: PassNone
Dev Schema Upgrade SQLyyw-code/MallBase106—~544Automated safety check: PassMIT
SQLbonny/WordPress-Simple-History317—~381Automated safety check: NotesNone
SQLMicrock/ordinary-claude-skills404—~573Automated safety check: PassCustom licence

Similar skills

  • Ravendb

    ravendb/docs

    Read this before writing any RavenDB query, client call or /databases/ request.

    115 GitHub stars~2.3k tokensUpdated today
    DatabasesAuto-check passed
  • Php SQL Audit

    0xShe/PHP-Code-Audit-Skill

    PHP Web 源码 SQL 注入漏洞审计工具。从源码中识别所有 SQL 执行点并分析注入风险,输出可利用性分级、PoC 与修复建议(禁止省略)。

    402 GitHub starsUsed in 1 repo~668 tokens
    DatabasesAuto-check passed
  • Dev Schema Upgrade SQL

    yyw-code/MallBase

    MallBase 数据库真相源、正式字段与升级 SQL 规则;修改 backend/install/data/schema 或 demo seed、新增/改名字段、移除运行时字段探测,或用户明确要求已有库升级、本地 upgrade SQL、发布迁移和 SimpleSqlMigrationService 时使用。

    106 GitHub stars~544 tokensUpdated 2 mo ago
    DatabasesAuto-check passed
  • SQL

    bonny/WordPress-Simple-History

    Runs SQL queries against the WordPress development database.

    317 GitHub stars~381 tokensUpdated 2 days ago
    DatabasesAuto-check: notes
  • SQL

    Microck/ordinary-claude-skills

    Run SQL queries against the WordPress development database. An agent skill from Microck/ordinary-claude-skills.

    404 GitHub stars~573 tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • Php Injection Audit

    wgpsec/AboutSecurity

    PHP 源码注入类漏洞审计。当在 PHP 白盒审计中需要检测注入类漏洞时触发. An agent skill from wgpsec/AboutSecurity.

    1.8k GitHub stars~965 tokensUpdated yesterday
    DatabasesAuto-check passed

More from hostinger/api-mcp-server

All 8 skills in this repo
  • Audit Hosting

    hostinger/api-mcp-server

    Audit a Hostinger web hosting account (Shared, Cloud and Agency plans) and report what needs attention: every plan and website, SSL problems, broken or vulnerable WordPress installs, failed Node.js…

    159 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Connect Domain

    hostinger/api-mcp-server

    Connect a custom domain to a website on Hostinger web hosting (Shared, Cloud or Agency plans) end to end: attach the domain to the site, point DNS at Hostinger without breaking existing email or…

    159 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Deploy To Hosting

    hostinger/api-mcp-server

    Deploy an existing project to a website on Hostinger web hosting (Shared, Cloud or Agency plans) and keep it deployed: picks the right deploy for static sites, Node.js apps (Next.js, Nuxt, Express…

    159 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes
  • Hostinger Headless Entry

    hostinger/api-mcp-server

    Build a complete website on Hostinger from a single prompt — hosting, domain, and (optionally) a store with real checkout or a blog/CMS the owner edits in WordPress.

    159 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Maintain Wordpress

    hostinger/api-mcp-server

    Keep WordPress sites on Hostinger web hosting updated and secure: checks core, plugin and theme versions, known vulnerabilities and install health on one site or every site in the account, reports…

    159 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Troubleshoot Website

    hostinger/api-mcp-server

    Diagnose and fix a website on Hostinger web hosting (Shared, Cloud or Agency plans) that is down, slow, erroring, insecure or failing to build.

    159 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about Migrate To Hosting

What does Migrate To Hosting do?

Move an existing website from another host to Hostinger web hosting (Shared, Cloud or Agency plans) without downtime: WordPress sites from a files archive and SQL dump, static and PHP sites from an…. Migrate To Hosting is an agent skill from hostinger/api-mcp-server.js apps from source.

When should I use Migrate To Hosting?

Migrate To Hosting fits situations like: tasks that involve SQL.

How do I install Migrate To Hosting in Claude Code?

Run `npx skills add hostinger/api-mcp-server --skill migrate-to-hosting -a claude-code`. Or copy the skill folder (skills/migrate-to-hosting in hostinger/api-mcp-server) into .claude/skills/migrate-to-hosting in your project. Claude Code loads it when a task matches its description.

How do I install Migrate To Hosting in Codex?

Run `npx skills add hostinger/api-mcp-server --skill migrate-to-hosting -a codex`. Or copy the skill folder (skills/migrate-to-hosting in hostinger/api-mcp-server) into .agents/skills/migrate-to-hosting in your project. Codex loads it when a task matches its description.

Can I use Migrate To Hosting in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hostinger/api-mcp-server --skill migrate-to-hosting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-to-hosting, .gemini/skills/migrate-to-hosting, .github/skills/migrate-to-hosting and .opencode/skills/migrate-to-hosting in your project.

What does Migrate To Hosting need to run?

Going by SKILL.md and its folder, Migrate To Hosting needs the command-line tools its instructions call (curl and mysql). Our summary lists: Node.js.

Does Migrate To Hosting access the network?

SKILL.md names 1 domain. In commands or code: api.ipify.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Migrate To Hosting safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Migrate To Hosting use?

Migrate To Hosting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Migrate To Hosting use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Migrate To Hosting?

Skills that share tags, products or a category with Migrate To Hosting: Ravendb (ravendb/docs, 115 stars), Php SQL Audit (0xShe/PHP-Code-Audit-Skill, 402 stars), Dev Schema Upgrade SQL (yyw-code/MallBase, 106 stars) and SQL (bonny/WordPress-Simple-History, 317 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Migrate To Hosting?

hostinger (a GitHub organization) maintains it in hostinger/api-mcp-server, which has 159 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: hostinger/api-mcp-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.