Skip to main content
Glama
hostinger

hostinger-api-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEBUGNoEnable debug logging (true/false)false
API_TOKENYesYour API token, which will be sent in the Authorization header

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
hosting_importWordpressWebsiteA

Import a WordPress website from an archive file to a hosting server. This tool uploads a website archive (zip, tar, tar.gz, etc.) and a database dump (.sql file) to deploy a complete WordPress website. The archive will be extracted on the server automatically. Note: This process may take a while for larger sites. After upload completion, files are being extracted and the site will be available in a few minutes. The username will be automatically resolved from the domain.

hosting_deployWordpressPluginA

Deploy a WordPress plugin from a directory to a hosting server. This tool uploads all plugin files and triggers plugin deployment.

hosting_deployWordpressThemeA

Deploy a WordPress theme from a directory to a hosting server. This tool uploads all theme files and triggers theme deployment. The uploaded theme can optionally be activated after deployment.

hosting_deployJsApplicationA

Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.

hosting_deployStaticWebsiteA

Deploy a static website from an archive file to a hosting server. IMPORTANT: This tool only works for static websites with no build process. The archive must contain pre-built static files (HTML, CSS, JavaScript, images, etc.) ready to be served. If the website has a package.json file or requires a build command, use hosting_deployJsApplication instead. The archive will be extracted and deployed directly without any build steps. The username will be automatically resolved from the domain.

hosting_listJsDeploymentsA

List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.

hosting_showJsDeploymentLogsA

Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.

billing_getCatalogItemListV1A

Retrieve catalog items available for order.

Prices in catalog items is displayed as cents (without floating point), e.g: float 17.99 is displayed as integer 1799.

Use this endpoint to view available services and pricing before placing orders.

billing_setDefaultPaymentMethodV1A

Set the default payment method for your account.

Use this endpoint to configure the primary payment method for future orders.

billing_deletePaymentMethodV1A

Delete a payment method from your account.

Use this endpoint to remove unused payment methods from user accounts.

billing_getPaymentMethodListV1A

Retrieve available payment methods that can be used for placing new orders.

If you want to add new payment method, please use hPanel.

Use this endpoint to view available payment options before creating orders.

billing_getSubscriptionListV1A

Retrieve a list of all subscriptions associated with your account.

Use this endpoint to monitor active services and billing status.

billing_disableAutoRenewalV1B

Disable auto-renewal for a subscription.

Use this endpoint when disable auto-renewal for a subscription.

billing_enableAutoRenewalV1C

Enable auto-renewal for a subscription.

Use this endpoint when enable auto-renewal for a subscription.

DNS_getDNSSnapshotV1A

Retrieve particular DNS snapshot with contents of DNS zone records.

Use this endpoint to view historical DNS configurations for domains.

DNS_getDNSSnapshotListV1A

Retrieve DNS snapshots for a domain.

Use this endpoint to view available DNS backup points for restoration.

DNS_restoreDNSSnapshotV1A

Restore DNS zone to the selected snapshot.

Use this endpoint to revert domain DNS to a previous configuration.

DNS_getDNSRecordsV1A

Retrieve DNS zone records for a specific domain.

Use this endpoint to view current DNS configuration for domain management.

DNS_updateDNSRecordsV1A

Update DNS records for the selected domain.

Using overwrite = true will replace existing records with the provided ones. Otherwise existing records will be updated and new records will be added.

Use this endpoint to modify domain DNS configuration.

DNS_deleteDNSRecordsV1B

Delete DNS records for the selected domain.

To filter which records to delete, add the name of the record and type to the filter. Multiple filters can be provided with single request.

If you have multiple records with the same name and type, and you want to delete only part of them, refer to the Update zone records endpoint.

Use this endpoint to remove specific DNS records from domains.

DNS_resetDNSRecordsV1A

Reset DNS zone to the default records.

Use this endpoint to restore domain DNS to original configuration.

DNS_validateDNSRecordsV1A

Validate DNS records prior to update for the selected domain.

If the validation is successful, the response will contain 200 Success code. If there is validation error, the response will fail with 422 Validation error code.

Use this endpoint to verify DNS record validity before applying changes.

v2_getDomainVerificationsDIRECTA

Retrieve a list of pending and completed domain verifications.

domains_checkDomainAvailabilityV1A

Check availability of domain names across multiple TLDs.

Multiple TLDs can be checked at once. If you want alternative domains with response, provide only one TLD and set with_alternatives to true. TLDs should be provided without leading dot (e.g. com, net, org).

Endpoint has rate limit of 10 requests per minute.

Use this endpoint to verify domain availability before purchase.

domains_getDomainForwardingV1A

Retrieve domain forwarding data.

Use this endpoint to view current redirect configuration for domains.

domains_deleteDomainForwardingV1A

Delete domain forwarding data.

Use this endpoint to remove redirect configuration from domains.

domains_createDomainForwardingV1A

Create domain forwarding configuration.

Use this endpoint to set up domain redirects to other URLs.

domains_enableDomainLockV1A

Enable domain lock for the domain.

When domain lock is enabled, the domain cannot be transferred to another registrar without first disabling the lock.

Use this endpoint to secure domains against unauthorized transfers.

domains_disableDomainLockV1A

Disable domain lock for the domain.

Domain lock needs to be disabled before transferring the domain to another registrar.

Use this endpoint to prepare domains for transfer to other registrars.

domains_getDomainDetailsV1A

Retrieve detailed information for specified domain.

Use this endpoint to view comprehensive domain configuration and status.

domains_getDomainListV1A

Retrieve all domains associated with your account.

Use this endpoint to view user's domain portfolio.

domains_purchaseNewDomainV1A

Purchase and register a new domain name.

If registration fails, login to hPanel and check domain registration status.

If no payment method is provided, your default payment method will be used automatically.

If no WHOIS information is provided, default contact information for that TLD will be used. Before making request, ensure WHOIS information for desired TLD exists in your account.

Some TLDs require additional_details to be provided and these will be validated before completing purchase.

Use this endpoint to register new domains for users.

domains_enablePrivacyProtectionV1A

Enable privacy protection for the domain.

When privacy protection is enabled, domain owner's personal information is hidden from public WHOIS database.

Use this endpoint to protect domain owner's personal information from public view.

domains_disablePrivacyProtectionV1A

Disable privacy protection for the domain.

When privacy protection is disabled, domain owner's personal information is visible in public WHOIS database.

Use this endpoint to make domain owner's information publicly visible.

domains_updateDomainNameserversV1C

Set nameservers for a specified domain.

Be aware, that improper nameserver configuration can lead to the domain being unresolvable or unavailable.

Use this endpoint to configure custom DNS hosting for domains.

domains_getWHOISProfileV1A

Retrieve a WHOIS contact profile.

Use this endpoint to view domain registration contact information.

domains_deleteWHOISProfileV1A

Delete WHOIS contact profile.

Use this endpoint to remove unused contact profiles from account.

domains_getWHOISProfileListV1B

Retrieve WHOIS contact profiles.

Use this endpoint to view available contact profiles for domain registration.

domains_createWHOISProfileV1A

Create WHOIS contact profile.

Use this endpoint to add new contact information for domain registration.

domains_getWHOISProfileUsageV1A

Retrieve domain list where provided WHOIS contact profile is used.

Use this endpoint to view which domains use specific contact profiles.

hosting_changeDatabasePasswordV1A

Changes the password for the specified database user.

The database name must be the full name returned by the list databases endpoint. The password must also be updated in any website configuration that uses this database.

hosting_listAccountDatabasesV1A

Returns a paginated list of databases for the specified account.

Use the domain and is_assigned filters to find databases assigned to a specific domain.

hosting_createAccountDatabaseV1B

Creates a database with a database user and password for the specified account.

The database name and user are automatically prefixed with the account username when needed.

hosting_deleteAccountDatabaseV1A

Permanently deletes a database and its remote connections.

The database name must be the full name returned by the list databases endpoint.

hosting_repairDatabaseV1A

Repairs corrupted database tables asynchronously.

Use when database errors, crashes, or corruption are reported. The database name must be the full name returned by the list databases endpoint.

hosting_getPhpMyAdminLinkV1A

Returns a direct sign-on link to phpMyAdmin for the specified database.

Use this when a visual database interface is needed for SQL queries, imports, exports, or table management. The database name must be the full name returned by the list databases endpoint.

hosting_listAvailableDatacentersV1A

Retrieve a list of datacenters available for setting up hosting plans based on available datacenter capacity and hosting plan of your order. The first item in the list is the best match for your specific order requirements.

hosting_generateAFreeSubdomainV1A

Generate a unique free subdomain that can be used for hosting services without purchasing custom domains. Free subdomains allow you to start using hosting services immediately and you can always connect a custom domain to your site later.

hosting_listWebsiteParkedDomainsV1A

Retrieve all parked or alias domains created under the selected website.

Use this endpoint to inspect parked domain configuration for a specific website, including the parent domain and root directory assigned to each parked domain.

hosting_createWebsiteParkedDomainV1B

Create a parked or alias domain for the selected website.

Provide a domain name or IP address to park on the website so it serves the same content as the parent domain.

hosting_deleteWebsiteParkedDomainV1A

Delete an existing parked or alias domain from the selected website.

Use this endpoint to remove parked domains that are no longer needed.

hosting_listWebsiteSubdomainsV1A

Retrieve all subdomains created under the selected website.

Use this endpoint to inspect subdomain configuration for a specific website, including the parent domain and root directory assigned to each subdomain.

hosting_createWebsiteSubdomainV1A

Create a new subdomain for the selected website.

Provide a subdomain prefix and, optionally, a custom directory or the website public directory to use as the subdomain root.

hosting_deleteWebsiteSubdomainV1A

Delete an existing subdomain from the selected website.

Use this endpoint to remove subdomains that are no longer needed.

hosting_verifyDomainOwnershipV1A

Verify ownership of a single domain and return the verification status.

Use this endpoint to check if a domain is accessible for you before using it for new websites. If the domain is accessible, the response will have is_accessible: true. If not, add the given TXT record to your domain's DNS records and try verifying again. Keep in mind that it may take up to 10 minutes for new TXT DNS records to propagate.

Skip this verification when using Hostinger's free subdomains (*.hostingersite.com).

hosting_listNodeJSBuildsV1A

Retrieve a paginated list of Node.js build processes for a specific website.

Each build represents a single run of the Node.js build pipeline. Use the states query parameter to filter results by build state (pending, running, completed, failed). Use the uuid from a build to poll its output via the Get Node.js Build Logs endpoint.

hosting_createNodeJSBuildFromArchiveV1A

Upload a project archive, auto-detect build settings, and immediately start a Node.js build.

This is the recommended single-step approach for deploying a Node.js application. The archive is uploaded to the website's file storage, build settings are auto-detected from the package.json inside the archive, and the build process starts automatically. Optional override fields take precedence over auto-detected values. Maximum archive size is 50MB.

Before archiving, exclude node_modules/ and any build output directories (e.g. dist/, .next/, build/) — they are not needed because the build process runs the install step automatically, and including them unnecessarily increases the archive size. This also helps keep the archive well under the 50MB limit.

Example (zip):

zip -r archive.zip . --exclude "node_modules/*" --exclude "dist/*"

The returned build uuid can be used to poll progress and retrieve logs via the Get Node.js Build Logs endpoint.

hosting_getNodeJSBuildLogsV1A

Retrieve logs from a specific Node.js build process.

To stream live output while a build is running, poll this endpoint repeatedly while the build state is running, passing the previously returned lines count as from_line to fetch only new output since the last call. Log content may contain ANSI escape sequences (color codes).

hosting_listOrdersV1A

Retrieve a paginated list of orders accessible to the authenticated client.

This endpoint returns orders of your hosting accounts as well as orders of other client hosting accounts that have shared access with you.

Use the available query parameters to filter results by order statuses or specific order IDs for more targeted results.

hosting_listWebsitesV1A

Retrieve a paginated list of websites (main and addon types) accessible to the authenticated client.

This endpoint returns websites from your hosting accounts as well as websites from other client hosting accounts that have shared access with you.

Use the available query parameters to filter results by username, order ID, enabled status, or domain name for more targeted results.

hosting_createWebsiteV1A

Create a new website for the authenticated client.

Provide the domain name and associated order ID to create a new website. The datacenter_code parameter is required when creating the first website on a new hosting plan - this will set up and configure new hosting account in the selected datacenter.

Subsequent websites will be hosted on the same datacenter automatically.

Website creation takes up to a few minutes to complete. Check the websites list endpoint to see when your new website becomes available.

hosting_installWordPressV1A

Install WordPress on an existing website.

The website must already exist before calling this endpoint. To create a new website first, use POST /api/hosting/v1/websites and poll GET /api/hosting/v1/websites until it appears.

Call GET /api/hosting/v1/wordpress/installations filtered by username and domain before proceeding to check whether WordPress is already installed on the target domain/path. If WordPress already exists and overwrite is false (the default), the async job will fail.

This operation is asynchronous: a successful response only means the install job has been queued, not that WordPress is ready. Installation typically takes 1-2 minutes. Poll GET /api/hosting/v1/wordpress/installations filtered by username and domain to track progress. When the installation appears in that list, WordPress is ready.

hosting_listWordPressInstallationsV1A

List WordPress installations accessible to the authenticated client.

Use this endpoint to discover existing WordPress installations and to poll for installation status after calling the install endpoint. When a newly requested installation appears in this list, WordPress is ready. Filter by username and domain to narrow results to a specific website.

Each installation includes a valid flag and, when invalid, a validationError describing why.

reach_deleteAContactV1A

Delete a contact with the specified UUID.

This endpoint permanently removes a contact from the email marketing system.

reach_listContactGroupsV1B

Get a list of all contact groups.

This endpoint returns a list of contact groups that can be used to organize contacts.

reach_listContactsV1B

Get a list of contacts, optionally filtered by group and subscription status.

This endpoint returns a paginated list of contacts with their basic information. You can filter contacts by group UUID and subscription status.

reach_createANewContactV1A

Create a new contact in the email marketing system.

This endpoint allows you to create a new contact with basic information like name, email, and surname.

If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent.

reach_listSegmentsV1A

Get a list of all contact segments.

This endpoint returns a list of contact segments that can be used to organize contacts.

reach_createANewContactSegmentV1C

Create a new contact segment.

This endpoint allows creating a new contact segment that can be used to organize contacts. The segment can be configured with specific criteria like email, name, subscription status, etc.

reach_listSegmentContactsV1B

Retrieve contacts associated with a specific segment.

This endpoint allows you to fetch and filter contacts that belong to a particular segment, identified by its UUID.

reach_getSegmentDetailsV1B

Get details of a specific segment.

This endpoint retrieves information about a single segment identified by UUID. Segments are used to organize and group contacts based on specific criteria.

reach_createNewContactsV1B

Create a new contact in the email marketing system.

This endpoint allows you to create a new contact with basic information like name, email, and surname.

If double opt-in is enabled, the contact will be created with a pending status and a confirmation email will be sent.

reach_listProfilesV1A

This endpoint returns all profiles available to the client, including their basic information.

VPS_getDataCenterListV1A

Retrieve all available data centers.

Use this endpoint to view location options before deploying VPS instances.

VPS_getProjectContainersV1A

Retrieves a list of all containers belonging to a specific Docker Compose project on the virtual machine.

This endpoint returns detailed information about each container including their current status, port mappings, and runtime configuration.

Use this to monitor the health and state of all services within your Docker Compose project.

VPS_getProjectContentsV1A

Retrieves the complete project information including the docker-compose.yml file contents, project metadata, and current deployment status.

This endpoint provides the full configuration and state details of a specific Docker Compose project.

Use this to inspect project settings, review the compose file, or check the overall project health.

VPS_deleteProjectV1A

Completely removes a Docker Compose project from the virtual machine, stopping all containers and cleaning up associated resources including networks, volumes, and images.

This operation is irreversible and will delete all project data.

Use this when you want to permanently remove a project and free up system resources.

VPS_getProjectListV1A

Retrieves a list of all Docker Compose projects currently deployed on the virtual machine.

This endpoint returns basic information about each project including name, status, file path and list of containers with details about their names, image, status, health and ports. Container stats are omitted in this endpoint. If you need to get detailed information about container with stats included, use the Get project containers endpoint.

Use this to get an overview of all Docker projects on your VPS instance.

VPS_createNewProjectV1A

Deploy new project from docker-compose.yaml contents or download contents from URL.

URL can be Github repository url in format https://github.com/[user]/[repo] and it will be automatically resolved to docker-compose.yaml file in master branch. Any other URL provided must return docker-compose.yaml file contents.

If project with the same name already exists, existing project will be replaced.

VPS_getProjectLogsV1A

Retrieves aggregated log entries from all services within a Docker Compose project.

This endpoint returns recent log output from each container, organized by service name with timestamps. The response contains the last 300 log entries across all services.

Use this for debugging, monitoring application behavior, and troubleshooting issues across your entire project stack.

VPS_restartProjectV1A

Restarts all services in a Docker Compose project by stopping and starting containers in the correct dependency order.

This operation preserves data volumes and network configurations while refreshing the running containers.

Use this to apply configuration changes or recover from service failures.

VPS_startProjectV1A

Starts all services in a Docker Compose project that are currently stopped.

This operation brings up containers in the correct dependency order as defined in the compose file.

Use this to resume a project that was previously stopped or to start services after a system reboot.

VPS_stopProjectV1A

Stops all running services in a Docker Compose project while preserving container configurations and data volumes.

This operation gracefully shuts down containers in reverse dependency order.

Use this to temporarily halt a project without removing data or configurations.

VPS_updateProjectV1A

Updates a Docker Compose project by pulling the latest image versions and recreating containers with new configurations.

This operation preserves data volumes while applying changes from the compose file.

Use this to deploy application updates, apply configuration changes, or refresh container images to their latest versions.

VPS_activateFirewallV1A

Activate a firewall for a specified virtual machine.

Only one firewall can be active for a virtual machine at a time.

Use this endpoint to apply firewall rules to VPS instances.

VPS_deactivateFirewallV1C

Deactivate a firewall for a specified virtual machine.

Use this endpoint to remove firewall protection from VPS instances.

VPS_getFirewallDetailsV1A

Retrieve firewall by its ID and rules associated with it.

Use this endpoint to view specific firewall configuration and rules.

VPS_deleteFirewallV1A

Delete a specified firewall.

Any virtual machine that has this firewall activated will automatically have it deactivated.

Use this endpoint to remove unused firewall configurations.

VPS_getFirewallListV1B

Retrieve all available firewalls.

Use this endpoint to view existing firewall configurations.

VPS_createNewFirewallV1B

Create a new firewall.

Use this endpoint to set up new firewall configurations for VPS security.

VPS_updateFirewallRuleV1A

Update a specific firewall rule from a specified firewall.

Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.

Use this endpoint to modify existing firewall rules.

VPS_deleteFirewallRuleV1A

Delete a specific firewall rule from a specified firewall.

Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.

Use this endpoint to remove specific firewall rules.

VPS_createFirewallRuleV1A

Create new firewall rule for a specified firewall.

By default, the firewall drops all incoming traffic, which means you must add accept rules for all ports you want to use.

Any virtual machine that has this firewall activated will lose sync with the firewall and will have to be synced again manually.

Use this endpoint to add new security rules to firewalls.

VPS_syncFirewallV1A

Sync a firewall for a specified virtual machine.

Firewall can lose sync with virtual machine if the firewall has new rules added, removed or updated.

Use this endpoint to apply updated firewall rules to VPS instances.

VPS_getPostInstallScriptV1A

Retrieve post-install script by its ID.

Use this endpoint to view specific automation script details.

VPS_updatePostInstallScriptV1A

Update a specific post-install script.

Use this endpoint to modify existing automation scripts.

VPS_deletePostInstallScriptV1A

Delete a post-install script from your account.

Use this endpoint to remove unused automation scripts.

VPS_getPostInstallScriptsV1C

Retrieve post-install scripts associated with your account.

Use this endpoint to view available automation scripts for VPS deployment.

VPS_createPostInstallScriptV1A

Add a new post-install script to your account, which can then be used after virtual machine installation.

The script contents will be saved to the file /post_install with executable attribute set and will be executed once virtual machine is installed. The output of the script will be redirected to /post_install.log. Maximum script size is 48KB.

Use this endpoint to create automation scripts for VPS setup tasks.

VPS_attachPublicKeyV1A

Attach existing public keys from your account to a specified virtual machine.

Multiple keys can be attached to a single virtual machine.

Use this endpoint to enable SSH key authentication for VPS instances.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hostinger/api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server