Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs

ssh_find

Search for files on a remote SSH host. Specify directory, filename pattern, type, size, and depth without constructing the find command yourself.

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')
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 full burden. It does not disclose key behavioral traits such as authentication requirements, connection handling, side effects, or error behavior. The security warning about passwords is only in the schema, not the 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 sentences with no superfluous text. The first sentence delivers the core purpose, and the second justifies the tool's value. Perfectly front-loaded and succinct.

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?

Given the tool's complexity (SSH, many parameters, no output schema), the description is minimal. It lacks behavioral context like authentication, timeout behavior, and return format, but the schema covers parameters.

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 fully documents all 12 parameters. The description adds no new meaning beyond stating it wraps find; baseline 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 'Search for files on a remote host' with a specific verb and resource. It distinguishes from siblings like ssh_ls (listing) and ssh_exec (command execution) by focusing on the find command wrapper.

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 implies usage for file search tasks and contrasts with manual find syntax construction, but it does not explicitly exclude alternative tools or 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