mcp-with-ssh
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Operational mode (code, architect, ask, debug, test) | code |
| path | No | Custom project path | |
| folder | No | Custom folder name for the Memory Bank | memory-bank |
| remote | No | Whether to use remote server mode | |
| ssh-key | No | Path to SSH key for remote server authentication | ~/.ssh/your_ssh_key |
| remote-host | No | Hostname for remote server | |
| remote-path | No | Path on remote server for Memory Bank storage | |
| remote-user | No | Username for remote server |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_memory_bankC | Initialize a Memory Bank in the specified directory |
| set_memory_bank_pathB | Set a custom path for the Memory Bank |
| debug_mcp_configB | Debug the current MCP configuration |
| read_memory_bank_fileC | Read a file from the Memory Bank |
| write_memory_bank_fileC | Write to a Memory Bank file |
| list_memory_bank_filesC | List Memory Bank files |
| get_memory_bank_statusC | Check Memory Bank status |
| migrate_file_namingB | Migrate Memory Bank files from camelCase to kebab-case naming convention |
| track_progressC | Track progress and update Memory Bank files |
| update_active_contextC | Update the active context file |
| log_decisionC | Log a decision in the decision log |
| switch_modeD | Switches to a specific mode |
| get_current_modeC | Gets information about the current mode |
| process_umb_commandC | Processes the Update Memory Bank (UMB) command |
| complete_umbC | Completes the Update Memory Bank (UMB) process |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Product Context | Project overview and context |
| Active Context | Current project context and tasks |
| Progress | Project progress and milestones |
| Decision Log | Project decisions and rationale |
| System Patterns | System patterns and architecture |
TDQS
Scored across 15 tools
Most tools have distinct purposes, but there is notable overlap between 'complete_umb' and 'process_umb_command' which both handle UMB processes, and 'track_progress' and 'update_active_context' could be confused for similar context management tasks. Descriptions help clarify, but some ambiguity remains.
Tool names follow a consistent verb_noun pattern throughout, such as 'initialize_memory_bank' and 'read_memory_bank_file', with minor deviations like 'debug_mcp_config' using 'debug' instead of a more standard verb. Overall, the naming is predictable and readable.
With 15 tools, the count is well-scoped for managing a Memory Bank system, covering initialization, reading/writing files, status checks, mode switching, and debugging. Each tool appears to serve a specific function without unnecessary bloat.
The tool set provides comprehensive CRUD-like coverage for Memory Bank operations, including initialization, file management, status tracking, and mode control. Minor gaps may exist, such as lacking direct tools for deleting files or advanced configuration management, but core workflows are well-supported.