Skip to main content
Glama
simon-ami

Windows CLI MCP Server

create_ssh_connection

Establish SSH connections to remote systems using host, port, credentials, or private keys for secure command-line access through the Windows CLI MCP Server.

Instructions

Create a new SSH connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdNoID of the SSH connection
connectionConfigNo

Implementation Reference

  • The core handler function that executes the tool logic: loads the config, adds the new SSH connection, and saves the updated config.
    const createSSHConnection = (connectionId: string, connectionConfig: any): void => {
      const config = loadConfig();
      config.ssh.connections[connectionId] = connectionConfig;
      saveConfig(config);
    };
  • MCP tool schema definition including name, description, and input schema for validation in ListTools response.
    {
      name: "create_ssh_connection",
      description: "Create a new SSH connection",
      inputSchema: {
        type: "object",
        properties: {
          connectionId: {
            type: "string",
            description: "ID of the SSH connection"
          },
          connectionConfig: {
            type: "object",
            properties: {
              host: {
                type: "string",
                description: "Host of the SSH connection"
              },
              port: {
                type: "number",
                description: "Port of the SSH connection"
              },
              username: {
                type: "string",
                description: "Username for the SSH connection"
              },
              password: {
                type: "string",
                description: "Password for the SSH connection"
              },
              privateKeyPath: {
                type: "string",
                description: "Path to the private key for the SSH connection"
              }
            },
            required: ["connectionId", "connectionConfig"]
          }
        }
      }
    },
  • src/index.ts:820-833 (registration)
    Tool registration and dispatch in the CallToolRequest handler: parses arguments with Zod schema and invokes the handler function.
    case 'create_ssh_connection': {
      const args = z.object({
        connectionId: z.string(),
        connectionConfig: z.object({
          host: z.string(),
          port: z.number(),
          username: z.string(),
          password: z.string().optional(),
          privateKeyPath: z.string().optional(),
        })
      }).parse(request.params.arguments);
      createSSHConnection(args.connectionId, args.connectionConfig);
      return { content: [{ type: 'text', text: 'SSH connection created successfully.' }] };
    }
  • src/index.ts:26-26 (registration)
    Import statement that brings the handler function into the main index file for use in tool dispatch.
    import { createSSHConnection, readSSHConnections, updateSSHConnection, deleteSSHConnection } from './utils/sshManager.js';
  • Export statement making the handler function available for import.
    export { createSSHConnection, readSSHConnections, updateSSHConnection, deleteSSHConnection }; 
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this requires authentication, has side effects (e.g., storing credentials), involves rate limits, or what happens on success/failure. For a tool that likely handles sensitive SSH data, this is a significant gap in 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 a single, efficient sentence with zero waste—'Create a new SSH connection' is front-loaded and appropriately sized for its minimal content. It earns its place by stating the core purpose without unnecessary elaboration.

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 (SSH connection creation with nested objects), no annotations, no output schema, and incomplete parameter coverage, the description is inadequate. It doesn't explain what 'create' means operationally, return values, or error conditions, leaving critical gaps for a tool that likely involves network operations and credential handling.

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 50% (2 parameters total, with descriptions for nested properties but not top-level ones). The description adds no parameter semantics beyond the schema, which already documents host, port, etc., but doesn't clarify the relationship between 'connectionId' and 'connectionConfig'. Baseline 3 is appropriate as the schema does moderate work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new SSH connection' clearly states the action (create) and resource (SSH connection), but it's vague about what 'create' entails—does it establish a live connection, store configuration, or both? It doesn't differentiate from siblings like 'update_ssh_connection' or 'ssh_connect' (if present), leaving ambiguity in scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'update_ssh_connection', 'ssh_disconnect', and 'read_ssh_connections', the description lacks context on prerequisites (e.g., whether a connection must not exist) or when to choose creation over updating, offering no usage instructions.

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/simon-ami/win-cli-mcp-server'

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