Skip to main content
Glama
widjis
by widjis

ssh_save_credential

Store SSH credentials for secure reuse across multiple connections, supporting both password and private key authentication methods.

Instructions

Save SSH credentials for reuse

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credentialIdYesUnique identifier for this credential
hostYesSSH server hostname or IP address
portNoSSH port number
usernameYesSSH username
passwordNoSSH password (if not using key)
privateKeyPathNoPath to private key file
passphraseNoPassphrase for private key

Implementation Reference

  • Main execution logic for the 'ssh_save_credential' tool: parses args with schema, validates uniqueness and auth method, stores credential in in-memory Map, returns success response.
    private async handleSaveCredential(args: unknown) {
      const params = SaveCredentialSchema.parse(args);
      
      if (credentialStore.has(params.credentialId)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Credential ID '${params.credentialId}' already exists`
        );
      }
    
      if (!params.password && !params.privateKeyPath) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Either password or privateKeyPath must be provided'
        );
      }
    
      const credential: StoredCredential = {
        host: params.host,
        port: params.port || 22,
        username: params.username,
        password: params.password,
        privateKeyPath: params.privateKeyPath,
        passphrase: params.passphrase,
        createdAt: new Date().toISOString(),
        lastUsed: new Date().toISOString()
      };
    
      credentialStore.set(params.credentialId, credential);
    
      return {
        content: [
          {
            type: 'text',
            text: `Credential '${params.credentialId}' saved successfully for ${params.username}@${params.host}:${params.port || 22}`,
          },
        ],
      };
    }
  • Zod input schema defining parameters for saving SSH credentials: credentialId (required), host, port (default 22), username (required), optional password/privateKeyPath/passphrase.
    const SaveCredentialSchema = z.object({
      credentialId: z.string().describe('Unique identifier for this credential'),
      host: z.string().describe('SSH server hostname or IP address'),
      port: z.number().default(22).describe('SSH port number'),
      username: z.string().describe('SSH username'),
      password: z.string().optional().describe('SSH password (if not using key)'),
      privateKeyPath: z.string().optional().describe('Path to private key file'),
      passphrase: z.string().optional().describe('Passphrase for private key')
    });
  • src/index.ts:372-387 (registration)
    Tool definition in ListTools response: name, description, and JSON schema mirroring the Zod schema.
      name: 'ssh_save_credential',
      description: 'Save SSH credentials for reuse',
      inputSchema: {
        type: 'object',
        properties: {
          credentialId: { type: 'string', description: 'Unique identifier for this credential' },
          host: { type: 'string', description: 'SSH server hostname or IP address' },
          port: { type: 'number', default: 22, description: 'SSH port number' },
          username: { type: 'string', description: 'SSH username' },
          password: { type: 'string', description: 'SSH password (if not using key)' },
          privateKeyPath: { type: 'string', description: 'Path to private key file' },
          passphrase: { type: 'string', description: 'Passphrase for private key' }
        },
        required: ['credentialId', 'host', 'username']
      },
    },
  • src/index.ts:505-506 (registration)
    Dispatch case in CallToolRequest handler mapping 'ssh_save_credential' name to handleSaveCredential method.
    case 'ssh_save_credential':
      return await this.handleSaveCredential(args);
  • In-memory Map storing saved credentials, key: credentialId, value: StoredCredential object.
    const credentialStore = new Map<string, StoredCredential>();
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 states the tool saves credentials but lacks critical behavioral details: where credentials are stored (e.g., in-memory, file, database), security implications (e.g., encryption, persistence), whether it overwrites existing credentials with the same ID, or what happens on success/failure. This is inadequate for a tool handling sensitive data.

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 no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by conveying the essential action and resource.

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 no annotations and no output schema, the description is incomplete for a tool that handles sensitive SSH credentials. It misses key context: storage method, security behavior, interaction with sibling tools (e.g., ssh_list_credentials), and what 'reuse' entails. For a 7-parameter mutation tool, this leaves significant gaps.

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 7 parameters. The description adds no parameter-specific information beyond implying credential persistence. Baseline 3 is appropriate since the schema handles parameter semantics, though the description doesn't compensate for any gaps (none exist).

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

Purpose4/5

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

The description clearly states the action ('Save') and resource ('SSH credentials for reuse'), making the purpose understandable. It doesn't explicitly distinguish from siblings like ssh_delete_credential or ssh_list_credentials, but the verb 'Save' implies creation/persistence versus deletion or listing.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to save credentials before using ssh_connect_with_credential), exclusions, or comparisons to other credential-related tools like ssh_delete_credential or ssh_list_credentials.

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/widjis/mcp-ssh'

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