Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_find

Search for files on a remote host over SSH with structured filters for name, type, size, and modification time, without manual command construction.

Instructions

Search for files on a remote host. Wraps the find command with structured parameters so you don't have to construct find syntax manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesSSH hostname or IP address
nameNoFilename pattern with wildcards (e.g. '*.log', 'config.*')
pathYesDirectory to search in (e.g. /var/log, /home/user)
portNoSSH port (default: 22)
typeNoFile type: f=file, d=directory, l=symlink
newerNoReference file path -- find matches files modified more recently than this file
maxsizeNoMaximum file size (e.g. '10M', '500k')
minsizeNoMinimum file size (e.g. '1M', '100k')
timeoutNoCommand timeout in milliseconds (default: 30000). Also the longest the call waits for a free connection-pool slot (SSH_MCP_MAX_POOL_SIZE, default 100) before the command starts; the wait and the command are bounded separately.
maxdepthNoMaximum directory depth to search
passwordNoSSH password. STRONGLY prefer key-based auth (privateKeyPath or ssh-agent). Passwords pass through MCP protocol frames as plaintext and may be logged by the transport or host process.
usernameNoSSH username (default: current user)
privateKeyPathNoPath to SSH private key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • changedInput schema / properties / timeout / description
      Previous value: -"Command timeout in milliseconds (default: 30000)"New value: +"Command timeout in milliseconds (default: 30000). Also the longest the call waits for a free connection-pool slot (SSH_MCP_MAX_POOL_SIZE, default 100) before the command starts; the wait and the command are bounded separately."
  2. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / newer
      Added value: +{
+  "description": "Reference file path -- find matches files modified more recently than this file",
+  "type": "string"
+}
  3. Addedv0.9.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose that the operation is read-only, nor does it mention authentication requirements, timeouts, or connection behaviors. The parameter descriptions cover some details (e.g., password plaintext risk, timeout), but the main description omits any behavioral context.

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?

The description is two sentences, concise, and front-loaded with the purpose. It is not overlong, though it sacrifices substantive guidance for brevity.

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?

For a tool with 13 parameters, no output schema, and no annotations, the description is incomplete. It does not describe what the tool returns (e.g., list of file paths) nor any prerequisites like SSH connectivity or authentication setup, leaving the agent without essential context for correct invocation.

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%, so each parameter has a description. The tool description adds little beyond 'structured parameters' and does not elaborate on parameter semantics beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states 'Search for files on a remote host' with a specific verb and resource, and mentions wrapping the find command. It does not explicitly differentiate from sibling tools like ssh_ls or ssh_stat, but the core purpose is unambiguous.

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 for find-like searches ('Wraps the find command with structured parameters so you don't have to construct find syntax manually') but does not explicitly state when to prefer this over ssh_ls or ssh_exec, nor does it provide exclusion criteria.

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