Skip to main content
Glama
Sign In
claude-ssh-mcp

claude-ssh-mcp

by MaraBank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ssh_execute

Execute shell commands on a remote server via an existing SSH session, automating remote command execution without manual login.

Instructions

Execute a command on a connected remote server.

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": {
      "sessionName": "<sessionName>",
      "command": "<command>"
    },
    "name": "ssh_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNameYesSession to run the command on
commandYesShell command to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must carry behavioral info. Only mentions 'connected remote server', implying a session is needed, but does not disclose behavior such as blocking, output handling, error states, or whether it returns exit codes.

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

Conciseness4/5

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

Single sentence, concise and front-loaded. Could be more informative while remaining concise.

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

Completeness2/5

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

No output schema and no annotations. The description lacks details on output format (stdout/stderr), whether it returns any data, or if an active session is required. Incomplete for a command execution tool.

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% (both parameters have descriptions). The description adds no extra meaning beyond the schema; baseline 3 is appropriate.

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

Purpose4/5

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

Description clearly states the verb 'Execute' and the resource 'command on a connected remote server'. It differentiates from sibling tools like ssh_download by specifying execution, but does not explicitly contrast with other commands.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like ssh_transfer or ssh_list_files. No mention of prerequisites (e.g., need to establish a session via ssh_connect).

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

Deploy Server

Other Tools