OVHcloud MCP Server

ovh_ssh_exec

Run shell commands on any remote server via SSH, using environment variables for default credentials or override them per execution.

Instructions

Execute a command on a remote server via SSH. Uses env defaults (SSH_HOST, SSH_USER, SSH_PASSWORD/SSH_PRIVATE_KEY_FILE) or per-call overrides.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "ovh_ssh_exec"
  }
}

Input Schema

Name	Required	Description
`command`	Yes	Shell command to execute on the remote server
`host`	No	SSH host (default: SSH_HOST env)
`port`	No	SSH port (default: SSH_PORT env or 22)
`username`	No	SSH username (default: SSH_USER env)
`password`	No	SSH password (default: SSH_PASSWORD env)
`privateKeyFile`	No	Path to SSH private key file
`timeout`	No	Exec timeout in ms

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jun 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It states the tool executes commands via SSH but does not mention whether it returns stdout/stderr, exit codes, or the synchronous nature of execution. Basic transparency but incomplete for a command execution tool.

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?

The description is two sentences: one for the purpose and one for configuration. Every word earns its place—no fluff, front-loaded with action.

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, the description should mention what the tool returns (e.g., stdout/stderr) since no output schema exists. It is missing this critical information, making it incomplete despite the tool's simplicity.

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 coverage is 100% with each parameter described. The description adds context about environment variable overrides, but this is already implicit in schema defaults. It does not add significant new meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'Execute a command on a remote server via SSH', specifying the verb (execute) and resource (command on remote server). It distinguishes from siblings like ovh_ssh_check (SSH check) and VPS tools by focusing on arbitrary command execution.

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

Usage Guidelines4/5

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

The description explains when to use it (execute SSH command) and provides context about environment variable defaults and per-call overrides. However, it does not explicitly state when not to use it or mention alternatives like ovh_ssh_check for connectivity tests, missing a clear exclusion.

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