hostinger-api-mcp

Created By
hostingera year ago
Overview

What is Hostinger API MCP?

Hostinger API MCP is a Model Context Protocol (MCP) server designed to facilitate interactions with the Hostinger API, enabling developers to integrate various functionalities into their applications.

How to use Hostinger API MCP?

To use the Hostinger API MCP, install it via npm, yarn, or pnpm, and configure it with your API token. You can then connect to the server using compatible clients like Claude.js.

Key features of Hostinger API MCP?

  • Implements Model Context Protocol (MCP) for seamless API interactions.
  • Provides various endpoints for managing billing, DNS, and virtual machines.
  • Supports multiple package managers for easy installation.

Use cases of Hostinger API MCP?

  1. Automating billing processes for services.
  2. Managing DNS records programmatically.
  3. Controlling virtual machines through API calls.

FAQ from Hostinger API MCP?

  • What is the minimum Node.js version required?

Node.js version 20 or higher is required.

  • Is there a way to update the MCP server?

Yes, you can update it using npm, yarn, or pnpm commands.

  • Can I use this with any MCP-compatible consumer?

Yes, it can be used with any MCP-compatible consumer like Claude.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hostinger
Star
13
Language
JavaScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago