Skip to main content
Glama
deenesjakoruzh
ohvenkat

hostinger-ssh-mcp

by ohvenkat
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

# hostinger-ssh-mcp

An MCP (Model Context Protocol) server that connects Claude Code to a Hostinger VPS via SSH. Run shell commands on your VPS directly from the Claude Code chat interface in VS Code.

## Prerequisites

- [Claude Code](https://docs.anthropic.com/en/docs/claude-code/overview) installed

- A Hostinger VPS (or any Linux VPS) with SSH access

- Node.js v18 or higher

## Installation

### 1. Install the package


npm install -g hostinger-ssh-mcp

### 2. Create a .env file

Create a .env file in the package directory with your VPS credentials:


VPS\_HOST=your\_vps\_ip\_address

VPS\_USER=your\_vps\_username

VPS\_PASS=your\_vps\_password

### 3. Register with Claude Code


claude mcp add hostinger-vps --scope user -- npx hostinger-ssh-mcp

### 4. Verify the connection


claude mcp list

You should see hostinger-vps: ✓ Connected.

## Usage

In the Claude Code chat panel in VS Code, you can now run commands on your VPS naturally:

- *"Use run_command to check disk space on the VPS"*

- *"Use run_command to show running Python processes"*

- *"Use run_command to tail the last 50 lines of ~/mybot/bot.log"*

## Security Notes

- Never commit your .env file to version control

- Consider setting up SSH key authentication instead of password for production use

- The .gitignore included in this package excludes .env automatically

## License

MIT

Available Tools

1 tool
run_commandA

Run a shell command on the Hostinger VPS via SSH

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYesThe shell command to run

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it runs a command, but does not disclose potential side effects (destructive commands), permission requirements, user context, or failure modes. For an operation that executes arbitrary shell code, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that is front-loaded with the core action and target. There is zero redundancy, and every word contributes to understanding the tool's purpose. It is appropriately sized for a simple one-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple command-execution tool with a fully documented parameter and no output schema, the description is minimally adequate. However, it does not mention whether output is returned, how errors are handled, or any security considerations (e.g., requiring sudo or being non-interactive). Given that it executes arbitrary shell commands, these details would materially improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single parameter's description ('The shell command to run') already explains its meaning. The tool description adds no additional context beyond the schema, so it meets the baseline of 3 but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Run a shell command') and the specific target environment ('on the Hostinger VPS via SSH'), providing a specific verb and resource. Even without siblings, the purpose is unambiguous and immediately distinguishable from any other tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a shell command needs to be executed on the VPS, but it provides no explicit context about when to use it versus alternatives (though none are listed as siblings). There is no mention of prerequisites, limitations, or scenarios where this tool might not be appropriate, leaving usage guidance solely to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedrun_command
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap. The single tool's purpose is clearly distinct by virtue of being the only option.

Naming Consistency5/5

The tool name 'run_command' follows a clear verb_noun pattern. Even without other tools to compare against, the naming is descriptive and consistent with common conventions.

Tool Count3/5

A single tool is borderline for a server named 'hostinger-ssh-mcp'. While it covers the core action of running SSH commands, the scope feels thin compared to typical SSH-related MCP servers that often include file transfer or session management tools.

Completeness4/5

The run_command tool can execute arbitrary shell commands, making it functionally versatile and capable of covering most typical operations (e.g., file manipulation, process management). However, it lacks specialized features like secure file upload/download or interactive session handling, which are minor gaps for an SSH-focused server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • SSH Remote MCP Server

    nqmn
    A
    license
    A
    quality
    C
    maintenance
    Enables SSH remote access to servers through Claude, allowing users to execute commands, transfer files via SFTP, and manage multiple remote connections using natural language.
    12
    8
    MIT

  • SSH MCP Server

    mertcankaraoglu
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables managing Ubuntu/Linux servers through natural language by establishing SSH connections and executing remote commands. Supports real-time command execution and output through Claude Desktop or Cursor IDE.
    14
    -

  • MCP SSH Server

    austinzq
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables Claude Code to control remote servers via SSH for automated deployment, testing, and operations, including command execution and file transfer.
    4
    -

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/ohvenkat/hostinger-ssh-mcp'

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