Skip to main content
Glama
YawLabs

SSH MCP Server

by YawLabs

ssh_config_lookup

Resolve the effective SSH configuration for any host. Displays hostname, user, port, identity files, proxy settings, and all options from ~/.ssh/config.

Instructions

Resolve the effective SSH configuration for a host. Shows hostname, user, port, identity files, proxy settings, and all other options from ~/.ssh/config. Use this to understand how SSH will connect to a host.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesSSH hostname or IP address

Implementation Reference

  • The handler function for the 'ssh_config_lookup' tool. Calls configLookup(host) and formats the result into a human-readable output showing hostname, user, port, identity files, proxy settings.
    async ({ host }) => {
      const result = configLookup(host);
      if ("error" in result) {
        return { content: [{ type: "text", text: result.error }], isError: true };
      }
    
      const lines: string[] = [`SSH config for "${host}":`, ""];
      lines.push(`  Hostname: ${result.hostname}`);
      lines.push(`  User: ${result.user}`);
      lines.push(`  Port: ${result.port}`);
      if (result.identityFile.length > 0) {
        lines.push(`  Identity files: ${result.identityFile.join(", ")}`);
      }
      if (result.proxyJump) lines.push(`  ProxyJump: ${result.proxyJump}`);
      if (result.proxyCommand) lines.push(`  ProxyCommand: ${result.proxyCommand}`);
      return { content: [{ type: "text", text: lines.join("\n") }] };
    },
  • src/tools.ts:235-258 (registration)
    Registration of the 'ssh_config_lookup' tool on the MCP server using server.tool(), with description and schema (host: HostSchema).
    server.tool(
      "ssh_config_lookup",
      "Resolve the effective SSH configuration for a host. Shows hostname, user, port, identity files, proxy settings, and all other options from ~/.ssh/config. Use this to understand how SSH will connect to a host.",
      {
        host: HostSchema,
      },
      async ({ host }) => {
        const result = configLookup(host);
        if ("error" in result) {
          return { content: [{ type: "text", text: result.error }], isError: true };
        }
    
        const lines: string[] = [`SSH config for "${host}":`, ""];
        lines.push(`  Hostname: ${result.hostname}`);
        lines.push(`  User: ${result.user}`);
        lines.push(`  Port: ${result.port}`);
        if (result.identityFile.length > 0) {
          lines.push(`  Identity files: ${result.identityFile.join(", ")}`);
        }
        if (result.proxyJump) lines.push(`  ProxyJump: ${result.proxyJump}`);
        if (result.proxyCommand) lines.push(`  ProxyCommand: ${result.proxyCommand}`);
        return { content: [{ type: "text", text: lines.join("\n") }] };
      },
    );
  • The ConfigLookupResult interface that defines the shape of the data returned by configLookup, used by the tool handler to format output.
    export interface ConfigLookupResult {
      hostname: string;
      user: string;
      port: string;
      identityFile: string[];
      proxyJump?: string;
      proxyCommand?: string;
      all: Record<string, string>;
      raw: string;
  • The configLookup function that executes 'ssh -G <host>' and parses the output via parseSshConfigOutput, returning the effective SSH configuration.
    export function configLookup(host: string): ConfigLookupResult | { error: string } {
      if (!isValidHostname(host)) {
        return { error: `Invalid hostname: "${host}"` };
      }
    
      const { stdout, ok } = runArgs("ssh", ["-G", host]);
      if (!ok) {
        return { error: `Failed to resolve SSH config for ${host}: ${stdout}` };
      }
    
      const { all, identityFiles } = parseSshConfigOutput(stdout);
    
      return {
        hostname: all.hostname || host,
        user: all.user || "",
        port: all.port || "22",
        identityFile: identityFiles,
        proxyJump: all.proxyjump && all.proxyjump !== "none" ? all.proxyjump : undefined,
        proxyCommand: all.proxycommand && all.proxycommand !== "none" ? all.proxycommand : undefined,
        all,
        raw: stdout,
      };
    }
  • The parseSshConfigOutput helper that parses the raw 'ssh -G' stdout into a key-value map and extracts identity files.
    export function parseSshConfigOutput(stdout: string): {
      all: Record<string, string>;
      identityFiles: string[];
    } {
      const all: Record<string, string> = {};
      const identityFiles: string[] = [];
    
      for (const line of stdout.split("\n")) {
        const spaceIdx = line.indexOf(" ");
        if (spaceIdx > 0) {
          const key = line.substring(0, spaceIdx);
          const value = line.substring(spaceIdx + 1);
          if (key === "identityfile") {
            identityFiles.push(value);
          } else {
            all[key] = value;
          }
        }
      }
    
      return { all, identityFiles };
    }
Behavior4/5

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

With no annotations, the description carries full burden. It describes the tool as reading config (resolve, shows), implying no side effects. It could explicitly state it's read-only, but the verbs are clear enough.

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, front-loading the action and including a usage directive. Every word adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description adequately covers what the tool does and what it returns. It lacks error handling details, but that is acceptable at this complexity level.

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?

The sole parameter 'host' is fully described in the schema (SSH hostname or IP address). The description adds minimal extra meaning, as it simply uses 'host' in context. Baseline of 3 is appropriate given 100% schema coverage.

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 it resolves the effective SSH configuration for a host, listing specific config items (hostname, user, port, etc.). It distinguishes from sibling tools like ssh_exec or ssh_download by focusing on config lookup.

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 says 'Use this to understand how SSH will connect to a host,' providing context for usage. However, it does not mention when not to use it or suggest alternative tools such as ssh_diagnose for troubleshooting.

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