
Hostinger Ssh Mcp
io.github.ohvenkatPublished by GitHub account ohvenkatv1.0.2Updated Oct 24, 2026
MCP server for connecting Claude Code to a Hostinger VPS via SSH
Overview
A local MCP server that lets Claude Code run shell commands on a Hostinger or other Linux VPS over SSH.
- What you can do
- Run shell commands on a remote VPS over SSH from the chat interface, such as checking disk space, listing running processes, or tailing log files.
- When to use it
- Useful when you want an assistant to inspect or operate a Hostinger or other Linux VPS from Claude Code without opening a separate terminal session.
- Requirements
- Node.js v18 or higher, Claude Code, and a Linux VPS with SSH access. Credentials are supplied through the environment variables VPS_HOST, VPS_USER and VPS_PASS, typically in a .env file in the package directory.
Installation
In SourceWeft
- Open Hostinger Ssh Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
# 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
### 2. Create a .env file
Create a .env file in the package directory with your VPS credentials:
### 3. Register with Claude Code
### 4. Verify the connection
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
Source: README.md at commit f4615da
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.