vpsnet-mcp 1.0.2 → 1.0.3

package/README.md

@@ -1,6 +1,6 @@
 # vpsnet-mcp
 
-[Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for managing [VPSnet.com](https://www.vpsnet.com) virtual private servers. Gives AI assistants full control over your VPS infrastructure — start/stop servers, change plans, manage DNS, deploy SSH keys, order new servers, and more.
+[Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for managing [VPSnet.com](https://www.vpsnet.com) virtual private servers. Gives AI assistants full control over your VPS infrastructure — order servers, manage plans, deploy SSH keys, and directly access your servers via SSH for software installation and configuration.
 
 ## Features
 
@@ -9,11 +9,27 @@
 - VPS lifecycle (start, stop, restart, reinstall OS)
 - Plan changes (free upgrades/downgrades)
 - DNS (rDNS/PTR records)
-- SSH key & API key management
+- SSH key management — deploy keys and gain direct server access
+- API key management
 - Backups, billing, invoices
 - Ordering new VPS instances
 - System status & pricing
 
+## SSH access workflow
+
+This MCP server manages your VPS infrastructure through the VPSnet.com API, including SSH key provisioning. Once an SSH key is deployed to a VPS, the AI assistant can connect directly using its environment's terminal (e.g. Claude Code's Bash tool, Cline's terminal).
+
+**Typical flow:**
+
+1. AI reads the local machine's public key (`~/.ssh/id_rsa.pub`)
+2. Uploads it to VPSnet.com via `create_ssh_key`
+3. Deploys it to a VPS via `deploy_ssh_key` (or passes it when ordering with `order_service`)
+4. Connects directly: `ssh root@<vps_ip>`
+
+Most AI coding environments (Claude Code, Cline, Cursor, Codex) have built-in terminal access, so the AI can SSH into your VPS immediately after deploying a key — no extra tools needed.
+
+For environments without native SSH access, consider pairing this with a dedicated SSH MCP server for direct server connectivity.
+
 ## Requirements
 
 - Node.js 18 or newer

package/build/index.js

@@ -18,16 +18,27 @@ const server = new McpServer({ name: "vpsnet", version: "1.0.0" }, {
         "After placing an order, wait 10-30 seconds before attempting SSH — the VPS needs time to boot and start SSH daemon.",
         "",
         "## SSH key workflow (IMPORTANT for deploying software to VPS)",
-        "When ordering or accessing a VPS, PREFER using sshKey over rootPassword — unless on Windows without an SSH client.",
-        "To access a VPS via SSH, you MUST use YOUR OWN local machine's SSH key:",
-        "1. Read the local machine's public key from ~/.ssh/id_rsa.pub or ~/.ssh/id_ed25519.pub",
-        "2. Upload it via create_ssh_key(name, public_key) — name it descriptively e.g. 'claude-code-local'",
-        "3. Deploy it to the VPS via deploy_ssh_key(orderNo, ssh_key_id) OR pass sshKey when ordering",
-        "4. Then SSH directly: ssh root@<vps_ip>",
-        "NEVER use someone else's SSH key — always read from the local machine where you are running.",
-        "Only fall back to rootPassword if the local machine has no SSH key and no SSH client (e.g. Windows without OpenSSH).",
-        "Note: order_service uses 'sshKey' (camelCase) but deploy_ssh_key uses 'ssh_key' (snake_case) — different field names!",
-        "To deploy software inside a VPS: first deploy an SSH key to the VPS, then access it directly via SSH. If no SSH client is available (e.g. Windows without OpenSSH), use rootPassword instead and connect via the platform's console or other remote access.",
+        "",
+        "### When the user asks you to deploy, install, or configure something INSIDE a VPS:",
+        "You MUST deploy YOUR OWN SSH key first, then connect directly via SSH.",
+        "After deploying your key, you can INSTANTLY access the VPS — no extra tools needed.",
+        "Most AI environments (Claude Code, Cline, Cursor, Codex) have a built-in terminal/bash tool.",
+        "Use that terminal to run: ssh -o StrictHostKeyChecking=no root@<vps_ip>",
+        "",
+        "### Step-by-step SSH key flow:",
+        "1. Read YOUR local machine's public key from ~/.ssh/id_rsa.pub or ~/.ssh/id_ed25519.pub",
+        "2. Upload it via create_ssh_key(name, public_key) — name it descriptively e.g. 'claude-code-key'",
+        "3. Deploy it to the VPS via deploy_ssh_key(orderNo, ssh_key_id) OR pass sshKey when ordering a new VPS",
+        "4. SSH directly using your environment's terminal: ssh -o StrictHostKeyChecking=no root@<vps_ip>",
+        "5. Now you can run any commands inside the VPS (apt install, configure services, deploy apps, etc.)",
+        "",
+        "### Important SSH notes:",
+        "- ALWAYS prefer sshKey over rootPassword — it's more secure and enables direct access.",
+        "- NEVER use someone else's SSH key — always read from the local machine where you are running.",
+        "- Use -o StrictHostKeyChecking=no when connecting to newly created VPS to avoid host key prompts.",
+        "- order_service uses 'sshKey' (camelCase) but deploy_ssh_key uses 'ssh_key' (snake_case) — different field names!",
+        "- Only fall back to rootPassword if the local machine has no SSH key (e.g. Windows without OpenSSH).",
+        "- If your environment has no terminal/bash access at all, consider using a dedicated SSH MCP server for connectivity.",
         "",
         "## Plan changes",
         "Plan changes are FREE — remaining time is recalculated (upgrade = shorter expiry, downgrade = longer expiry).",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vpsnet-mcp",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "type": "module",
   "description": "MCP server for managing VPSnet.com virtual private servers",
   "bin": {