Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger

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

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{}
extensions
{
  "io.modelcontextprotocol/skills": {}
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Find API operations by keyword. Returns the best matches, each with its operation name, hints and inputSchema. Pass a result's operation and params matching its inputSchema to execute or multi-execute.

executeA

Run one API operation found with search. params is a flat object holding the operation's path, query and body parameters as described by its inputSchema.

multi-executeA

Run up to 20 API operations in order, stopping at the first failure. A params value that is exactly "$steps.." is replaced by that value from the result of earlier step (dot-separated keys; numbers index arrays), e.g. "$steps.0.0.id".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
audit-hosting/SKILL.md
connect-domain/SKILL.md
deploy-to-hosting/SKILL.md
hostinger-headless/SKILL.md
hostinger-headless/references/DATABASE.md
hostinger-headless/references/DEPLOYMENT.md
hostinger-headless/references/SETUP.md
hostinger-headless/references/STORE.md
hostinger-headless/references/WORDPRESS.md
maintain-wordpress/SKILL.md
migrate-to-hosting/SKILL.md
troubleshoot-website/SKILL.md

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Search is explicitly for discovery, execute for running one operation, and multi-execute for running up to 20 in order with dependency chaining. Their purposes are clearly distinct and non-overlapping, with descriptions that make the boundaries obvious.

Naming Consistency4/5

The names 'search', 'execute', and 'multi-execute' all use verb-based action words, but 'multi-execute' is a compound that deviates slightly from the simple verb pattern. The set is still predictable and readable overall.

Tool Count5/5

Three tools perfectly match the generic API gateway pattern: one for discovery, one for single execution, and one for batch execution. Each tool earns its place without redundancy or missing layers.

Completeness4/5

The set covers discovery, single execution, and chained batch execution, which is nearly complete for a meta-API gateway. Minor gaps include no continue-on-error option for multi-execute and no way to list all operations without a keyword.

Maintenance

ActivityActive
ResponsivenessUnresponsive