Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs

ssh_ls

List files in a remote directory over SFTP by specifying the hostname and absolute path.

Instructions

List files in a directory on a remote host via SFTP.

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.
pathYesAbsolute path to the remote directory

Implementation Reference

  • Registration and handler for the ssh_ls tool. Calls the listDir helper to list files via SFTP and joins results with newlines.
    server.tool(
      "ssh_ls",
      "List files in a directory on a remote host via SFTP.",
      {
        ...connectionParams,
        path: z.string().describe("Absolute path to the remote directory"),
      },
      async ({ path, ...conn }) => {
        return connectionPool.withConnection(conn, async (client) => {
          const files = await listDir(client, path);
          return { content: [{ type: "text", text: files.join("\n") }] };
        });
      },
    );
  • src/tools.ts:122-135 (registration)
    Tool registration for 'ssh_ls' using server.tool() with Zod schema for connection params and path.
    server.tool(
      "ssh_ls",
      "List files in a directory on a remote host via SFTP.",
      {
        ...connectionParams,
        path: z.string().describe("Absolute path to the remote directory"),
      },
      async ({ path, ...conn }) => {
        return connectionPool.withConnection(conn, async (client) => {
          const files = await listDir(client, path);
          return { content: [{ type: "text", text: files.join("\n") }] };
        });
      },
    );
  • Input schema for ssh_ls: spreads connectionParams (host, port, username, privateKeyPath, password) and adds a required 'path' string.
    {
      ...connectionParams,
      path: z.string().describe("Absolute path to the remote directory"),
    },
  • The listDir helper function that uses ssh2 SFTP client to read directory entries and return filenames.
    export async function listDir(client: Client, remotePath: string): Promise<string[]> {
      const sftp = await getSftp(client);
      try {
        return await new Promise((resolve, reject) => {
          sftp.readdir(remotePath, (err, list) => {
            if (err) return reject(err);
            resolve(list.map((item) => item.filename));
          });
        });
      } finally {
        sftp.end();
      }
    }
Behavior3/5

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

The description indicates a non-destructive read operation via SFTP, but does not cover authentication needs, error behavior (e.g., non-existent path), or output format. With no annotations, more detail would be helpful but this is minimal viable.

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 a single, clear sentence with no wasted words. It is appropriately front-loaded and 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?

The description does not specify output format (filenames only? details?), recursion/wildcard support, or performance considerations. Given the absence of output schema and six parameters, more context is needed for complete understanding.

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 has 100% description coverage on all 6 parameters, so the description adds negligible value beyond the schema. It mentions 'via SFTP' which hints at protocol, but no parameter-specific enhancements.

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 uses a specific verb ('List'), resource ('files in a directory'), and method ('via SFTP'), clearly distinguishing it from siblings like ssh_read_file or ssh_download.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description omits context like when to prefer this over ssh_exec for listing, though the SFTP mention implies a read-only operation.

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