Hostinger API Model Context Protocol

MCPOfficialOpen SourceMIT53.8

by hostinger • Workflow & Task Management

An MCP server for managing the Hostinger API, supporting various services like billing, domains, DNS, and VPS management.

Example Use Cases

1
Manage billing and payment methods for Hostinger services.
2
Configure domain settings and DNS records within the Hostinger platform.
3
Automate the deployment and management of virtual machines via Hostinger's API.

Description

The Hostinger API Model Context Protocol (MCP) server facilitates communication with the Hostinger API, offering a range of tools for managing hosting accounts, domain configurations, billing services, and virtual machines. It offers flexible transport options and an array of available tools tailored to various hosting management needs, making it ideal for automated control of Hostinger's services.

Capabilities(119 total)

Tools (119)

hosting_importWordpressWebsite

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.

domain:string*archivePath:string*databaseDump:string*

hosting_deployWordpressPlugin

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

domain:string*slug:string*pluginPath:string*

hosting_deployWordpressTheme

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.

domain:string*slug:string*themePath:string*activate:boolean

hosting_deployJsApplication

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.

domain:string*archivePath:string*removeArchive:boolean

hosting_deployStaticWebsite

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.

domain:string*archivePath:string*removeArchive:boolean

Quick Actions

View on GitHub

Security

Scanned 3 month(s) ago

Risk Level

MINIMAL

Read-only data retrieval, no side effects

Trust Score

D45/100

3/17 checks passed

Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.

Quick Stats

Service TypeMCP

Pricing ModelFree

Capabilities119 Tools / 0 Prompts / 0 Resources

Ownerhostinger

CategoryWorkflow & Task Management

DependenciesStandalone

Set Your Username