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_deployWordpressPluginC

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

hosting_deployWordpressThemeB

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_updateDNSRecordsV1B

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_deleteDNSRecordsV1C

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_resetDNSRecordsV1B

Reset DNS zone to the default records.

Use this endpoint to restore domain DNS to original configuration.

DNS_validateDNSRecordsV1B

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_getDomainVerificationsDIRECTB

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_createDomainForwardingV1B

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_updateDomainNameserversV1A

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_getWHOISProfileV1B

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_createWHOISProfileV1C

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.

ecommerce_getCustomStorefrontSetupInstructionsV1A

Retrieve step-by-step setup instructions, formatted as Markdown, for connecting a custom sales channel to your store and keeping your catalog, orders, shipping and payments in sync through the Ecommerce API.

ecommerce_enableManualPaymentMethodV1B

Enable a manual payment method so the store can accept orders without an online payment provider.

ecommerce_createDigitalProductV1B

Create a published digital product with a single variant and an optional external download link.

ecommerce_createPhysicalProductV1A

Create a published physical product with a single variant priced in the store currency.

ecommerce_listSalesChannelsV1B

List a store's active sales channels with their full metadata.

ecommerce_createCustomSalesChannelV1A

Create a custom sales channel for a store. Build your own frontend and keep your catalog, orders, shipping and payments in sync through the Ecommerce API.

ecommerce_updateSalesChannelV1A

Update a custom sales channel. The merchant-facing name and the public url (returned as the channel domain) can be changed. Pass null to clear a value.

ecommerce_setStoreShippingV1A

Set the flat-rate shipping price for a store, creating the shipping zone if it does not exist yet.

ecommerce_deleteStoreV1A

Soft-delete a store owned by your account.

The underlying store data is preserved; only the store is marked as deleted.

ecommerce_getStoresV1C

Retrieve the stores associated with your account.

ecommerce_createStoreV1C

Create a new store for your account.

A primary sales channel is created alongside the store.

ecommerce_getStoreMetadataV1A

Get a store's readiness metadata: whether payment methods and shipping are configured, plus its default currency. Useful to verify prerequisites before building a storefront.

horizons_createWebsiteV1A

Create new Hostinger Horizons website from the given message.\n Use this tool when user asks you to create a website, landing page, blog or any other type of application.\n This tool initiates the website creation process and returns a website URL and ID. The generation happens asynchronously.\n After invoking this tool, your chat reply must be EXACTLY 1 sentence summarizing that Hostinger Horizons is now creating their website and it will be ready in a few minutes and you should provide the website URL to the user immediately Do not write code.\n\nTo edit afterwards, users must go to Hostinger Horizons interface in the provided website URL. If the tool call fails with an error, you should provide a clear explanation of the error and do not generate code yourself in the chat. \n TECHNOLOGY STACK CONSTRAINTS (STRICTLY ENFORCED):\n The environment is limited to the following technologies. You MUST NOT use, suggest, or implement any technology outside this list:\n \n

  • Language: JavaScript ONLY.

  • Languages like TypeScript, Rust, Python, Java, PHP, etc., are STRICTLY PROHIBITED.\n

  • Framework: React.\n

  • Navigation: React Router.\n

  • Styling: TailwindCSS.\n

  • Components: shadcn/ui (built with @radix-ui primitives).\n

  • Icons: Lucide React.\n

  • Animations: Framer Motion.\n \n BACKEND & DATA STORAGE:\n

  • Horizons integrated backend is the EXCLUSIVE solution for persistent data storage, authentication, and database needs.\n

  • Local databases (SQLite, MySQL, etc.) are STRICTLY PROHIBITED.\n

  • Third-party services (Firebase, AWS Amplify) are allowed ONLY if explicitly requested by the user.\n \n MAPS:\n

  • OpenStreetMap is the default provider.\n

  • Alternative providers (Google Maps, Mapbox) are allowed ONLY if explicitly requested by the user.\n

horizons_getWebsiteV1A

Get a link for the user to edit their website in Hostinger Horizons interface.\n Use this tool when user wants to modify, edit or add new features to an existing website.\n Websites can only be edited in Hostinger Horizons interface in the provided website URL.

hosting_clearWebsiteCacheV1A

Permanently clears all server-side cache for the website at once. Use it when content was updated and needs to be visible immediately, or after making major changes.

Also purges the Hostinger CDN cache when CDN is enabled on the website. For a WordPress installation living in a subdirectory, pass the directory query parameter to clear its cache.

hosting_disableCachelessModeV1A

Turns off development (cacheless) mode and returns the website to normal caching. Use it after finishing development work to restore the performance benefits of caching.

hosting_disableWebsiteCacheV1A

Turns off server-side caching for the website until it is enabled again. May impact performance. Use it when experiencing cache-related issues; to temporarily bypass caching while developing or debugging, prefer enabling cacheless mode instead.

Does nothing if caching is already disabled.

hosting_enableCachelessModeV1A

Enables development (cacheless) mode where nothing is cached, effectively turning off all caching for the website. Use it while actively developing, testing changes, debugging issues, or when real-time updates must be visible. Disable cacheless mode afterwards to restore normal caching.

hosting_enableWebsiteCacheV1A

Turns on server-side caching for the website for better performance. Use it for faster page loads, reduced server load, or improved user experience. Recommended for production websites.

Does nothing if caching is already enabled.

hosting_listAccountCronJobsV1A

Returns the list of cron jobs configured for the specified account, including their schedule and command.

hosting_createAccountCronJobV1B

Creates a cron job for the specified account from a schedule expression and a command.

Returns the created cron job, including its uid, which is required to delete the cron job or fetch its output.

hosting_deleteAccountCronJobV1A

Permanently deletes the cron job identified by its uid.

The uid is returned by the list cron jobs endpoint.

hosting_getCronJobOutputV1A

Returns the output captured from the last execution of the cron job identified by its uid.

The uid is returned by the list cron jobs endpoint.

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_createAccountDatabaseV1A

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_createAccountDatabaseRemoteConnectionV1A

Allows a remote host to connect to the specified database.

Provide an IPv4/IPv6 address, or "%" to allow any host. The database name must be the full name returned by the list databases endpoint.

hosting_deleteAccountDatabaseRemoteConnectionV1A

Permanently removes a remote-access rule, revoking the given host's remote access to the database.

Identify the rule with the required ip query parameter (the IPv4/IPv6 address, or "%", exactly as returned by the list remote connections endpoint). The database name must be the full name returned by the list databases endpoint.

hosting_listAccountDatabaseRemoteConnectionsV1A

Returns the remote-access rules for the specified account: the remote hosts (IPv4/IPv6 addresses, or "%" for any host) allowed to connect to the account databases.

Use the domain filter to only return rules for databases assigned to a specific domain.

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_createWebsiteParkedDomainV1A

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_createWebsiteSubdomainV1B

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_deleteWebsiteSubdomainV1B

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_restartNode.jsApplicationV1A

Restarts the Node.js server process for the website. Does not rebuild or redeploy the application. Use it to apply environment or configuration changes, or to recover a hung application.

Only applicable to server-side applications (Express, Next.js, NestJS, etc.). Static front-end apps (React, Vue, Vite) have no persistent server process, so restarting them has no effect. Returns success even when the website has no server process to restart.

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_resetPHPExtensionsV1A

Resets all PHP extensions of the website to their default state.

Use it to recover from extension conflicts or restore the original configuration.

hosting_getPHPDetailsV1A

Returns the full PHP configuration for the website: current version, available versions (supported and unsupported), enabled/disabled extensions, options with their current value, default, type and the plan limit (max), and conflicting extension groups.

Use it to check the current PHP setup before updating the version, extensions or options.

hosting_getPHPInfoV1A

Returns the full phpinfo page (HTML) for the website.

Use it to debug PHP issues or inspect the complete PHP environment of the website.

hosting_updatePHPExtensionsV1A

Enables or disables PHP extensions (modules) for the website.

Use the Get PHP details endpoint to check the current extension states before changing them.

hosting_updatePHPOptionsV1A

Updates PHP options for the website (e.g. memory_limit, max_execution_time, upload_max_filesize). Only provide the options you want to change, inside the options object.

Values above the account plan limit are silently capped to that limit, so the request can succeed with a smaller applied value. Call the Get PHP details endpoint afterwards to read the applied value.

hosting_updatePHPVersionV1B

Changes the PHP version of the website.

Use the Get PHP details endpoint to see the versions available for the website.

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.

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_listContactsV1A

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_createANewContactV1B

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.

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