Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs

ssh_find

Search for files on a remote SSH host using structured parameters. Specify directory, filename pattern, type, size, and other filters without 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)
Behavior3/5

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

No annotations exist, so the description must disclose behavioral traits. It does not mention authentication requirements, that the operation is read-only, or potential side effects. However, the password parameter description provides a strong security warning. Overall moderate transparency.

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 long, front-loaded with purpose, and contains no extraneous information. Every word contributes meaning.

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?

Despite 13 parameters, the description lacks details on return format, result handling, or pagination. For a complex tool with no output schema, the description is too minimal to be fully complete.

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 the schema already explains each parameter's meaning. The description adds no additional parameter-level insight beyond the overall wrapper concept, leading to a baseline score of 3.

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 tool searches for files on a remote host by wrapping the find command. It distinguishes from siblings like ssh_exec or ssh_ls by focusing on structured file search without manual find syntax.

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 file searching and mentions wrapping find to avoid manual syntax, but it does not explicitly state when to use this tool versus alternatives like ssh_ls or ssh_stat, nor does it provide when-not-to-use guidance.

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