Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs

ssh_find

Search for files on a remote server by specifying directory, filename pattern, file type, size, or modification time, without manually writing find syntax.

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
portNoSSH port (default: 22)
usernameNoSSH username (default: current user)
privateKeyPathNoPath to SSH private key
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.
pathYesDirectory to search in (e.g. /var/log, /home/user)
nameNoFilename pattern with wildcards (e.g. '*.log', 'config.*')
typeNoFile type: f=file, d=directory, l=symlink
maxdepthNoMaximum directory depth to search
minsizeNoMinimum file size (e.g. '1M', '100k')
maxsizeNoMaximum file size (e.g. '10M', '500k')
newerNoReference file path -- find matches files modified more recently than this file
timeoutNoCommand timeout in milliseconds (default: 30000)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool wraps find but omits side effects (e.g., resource intensity), return format, error handling, or security considerations (though password warning is in schema, not description).

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?

Two concise sentences front-load the purpose with no wasted words. Every sentence earns its place.

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?

Given the complexity (13 parameters, no output schema), the description is too sparse. It does not explain return values, error behavior, or how results are presented. More context about the tool's behavior is needed.

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%, so baseline is 3. The description adds no extra meaning beyond the overall purpose; it does not augment understanding of individual parameters.

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 the verb 'Search for files' and resource 'on a remote host', distinguishing it from sibling tools by mentioning it wraps the find command, which is unique among the listed tools.

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 does not explicitly state when to use this tool versus alternatives. It implies usage for complex searches via find but lacks guidance on when not to use it (e.g., for simple listing, use ssh_ls). The parameter schema provides implicit context but description alone is insufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YawLabs/ssh-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server