remote-ssh-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity: list_sessions manages session enumeration, ssh_connect/disconnect handle connection lifecycle, ssh_exec runs commands, ssh_read_buffer retrieves output, and scp_download/upload handle file transfers. The descriptions clearly differentiate between session management, command execution, and file operations.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with clear prefixes: ssh_ for session/command operations, scp_ for file transfers, and list_ for enumeration. The naming is perfectly predictable and follows a logical convention throughout the set.
Tool Count5/5
With 7 tools, this server is well-scoped for remote SSH operations. Each tool earns its place by covering essential functions: connection management, command execution, output reading, file transfer, and session listing. The count is neither too sparse nor bloated for the domain.
Completeness4/5
The toolset provides excellent coverage for core SSH workflows: connect, execute, read output, transfer files, and manage sessions. A minor gap exists in advanced session features like interactive shell handling or terminal resizing, but agents can work around this with ssh_exec. The surface supports most common remote operations without dead ends.
Average 3/5 across 7 of 7 tools scored.
See the Tool Scores section below for per-tool breakdowns.
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Download') but doesn't cover critical aspects like authentication requirements (implied by 'session_id'), file transfer behavior (e.g., overwriting, error handling), or performance considerations (e.g., large files, network limits). This leaves significant gaps for a mutation tool that writes to the local filesystem.
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 that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, with no redundancy or fluff.
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 of a file download operation with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success (e.g., file saved locally) or failure (e.g., error messages), nor does it cover side effects like local file overwriting. For a tool that modifies the local filesystem, more behavioral context is needed to ensure safe and correct usage.
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%, with clear parameter descriptions in the schema itself. The description adds no additional parameter semantics beyond what's already documented (e.g., format examples, path conventions, or session lifecycle details). This meets the baseline score of 3 since the schema adequately covers parameter meanings.
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 ('Download') and resource ('a file from remote server via SFTP'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'scp_upload' or 'ssh_read_buffer', which would require mentioning it's specifically for file transfer rather than command execution or session management.
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 an active session from 'ssh_connect'), differentiate from 'scp_upload' (upload vs. download), or explain when to choose this over 'ssh_read_buffer' for reading files. Without such context, the agent must infer usage from tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the upload action but doesn't cover critical aspects like authentication requirements (implied by SFTP but not detailed), potential file overwriting behavior, error handling, or performance considerations like transfer speed or size limits. This leaves significant gaps in understanding how the tool behaves in practice.
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, direct sentence that efficiently conveys the core functionality without any fluff. It is front-loaded with the essential action and resource, making it easy to parse quickly. Every word earns its place, adhering perfectly to principles of conciseness and clear structure.
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 tool's complexity (involving file transfer over SFTP with session management), no annotations, and no output schema, the description is insufficiently complete. It lacks details on return values, error conditions, security implications, or how it integrates with sibling tools like 'ssh_connect' for session setup. This leaves too many unknowns for effective use in a broader context.
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 input schema has 100% description coverage, providing clear definitions for all three parameters ('session_id', 'local_path', 'remote_path'). The description adds no additional semantic context beyond what's in the schema, such as format examples or constraints. According to scoring rules, with high schema coverage, the baseline is 3 even without extra param info in the description.
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 ('Upload') and the resource ('a local file to remote server via SFTP'), making the purpose immediately understandable. It distinguishes itself from siblings like 'scp_download' by specifying the direction of transfer. However, it doesn't explicitly differentiate from other tools like 'ssh_exec' that might also involve file operations, keeping it from a perfect score.
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 like needing an active session (implied by 'session_id' but not stated), when to choose SFTP over other methods, or how it relates to siblings such as 'scp_download' for reverse operations. This lack of contextual advice leaves users guessing about optimal usage scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose if disconnection is destructive (e.g., terminates processes), requires specific permissions, has side effects, or what happens on success/failure. The description is minimal and misses critical context for a mutation tool.
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 zero wasted words. It's front-loaded and efficiently conveys the core action, making it easy to parse quickly.
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?
For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior, error handling, or integration with siblings (e.g., how to obtain session_id from 'list_sessions'), leaving significant gaps for agent usage.
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%, with the parameter 'session_id' documented in the schema. The description adds no additional meaning beyond implying the parameter identifies a session to disconnect, so it meets the baseline for high schema coverage without compensating value.
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 verb ('Disconnect') and resource ('SSH session'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ssh_connect' or 'list_sessions' beyond the obvious action difference, missing explicit contrast.
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 an active session from 'ssh_connect'), exclusions, or related tools like 'list_sessions' for identifying sessions to disconnect.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It states the basic action but lacks critical details: it doesn't mention whether this is a read-only or destructive operation (executing commands can modify remote systems), what happens on timeout (e.g., process termination), how output is returned (since no output schema exists), or error handling. For a command execution tool with zero annotation coverage, this leaves significant behavioral gaps.
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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, with no redundancy or fluff.
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 of SSH command execution (potentially destructive, requires session management), no annotations, and no output schema, the description is incomplete. It doesn't address critical context like return values (stdout/stderr), error conditions, security implications, or how it relates to sibling tools (e.g., ssh_connect as prerequisite). For a tool with 4 parameters and significant behavioral implications, this minimal description is inadequate.
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 all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify command syntax, timeout implications, or background behavior). This meets the baseline for high schema coverage but doesn't enhance understanding.
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 ('Execute a command') and target resource ('on a connected SSH session'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like ssh_read_buffer (which reads output) or scp_download/upload (file transfer), but the verb 'execute' is specific enough to imply command execution rather than other SSH operations.
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., requires an established session via ssh_connect), when to prefer background execution, or when other tools like ssh_read_buffer might be more appropriate for reading output. The agent must infer usage from the tool name and parameters alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool reads output but doesn't cover critical aspects like whether this requires specific permissions, if it's read-only (implied by 'Read' but not explicit), rate limits, or what happens if the session is inactive. This leaves significant gaps for safe and effective use.
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 that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it easy to parse quickly while conveying the essential action.
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 of SSH operations and lack of annotations or output schema, the description is incomplete. It doesn't explain return values (e.g., format of the buffer output), error conditions, or dependencies on other tools like 'ssh_connect'. For a tool interacting with session buffers, more context is needed for reliable use.
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%, with clear documentation for both parameters (session_id and lines). The description adds no additional parameter semantics beyond what's in the schema, such as format details or usage examples. This meets the baseline for high schema coverage but doesn't enhance understanding.
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 ('Read') and resource ('recent terminal output from session buffer'), making the tool's function immediately understandable. It doesn't explicitly differentiate from siblings like 'ssh_exec' (which executes commands) or 'list_sessions' (which lists sessions), but the specific focus on reading buffer output is clear.
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. For example, it doesn't mention prerequisites like needing an active SSH session or how it differs from 'ssh_exec' for retrieving output. Without such context, an agent might struggle to choose appropriately among sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, it doesn't specify what 'active' means (e.g., time threshold), whether the list includes metadata like session duration or user, or if there are rate limits. The description is minimal and lacks important behavioral context.
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 that states the core functionality without any fluff. It's appropriately sized for a simple list tool and front-loads the essential information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate but leaves gaps. It doesn't explain what constitutes an 'active' session, what format the output takes, or any behavioral constraints. For a read-only list tool, it meets basic needs but lacks completeness for reliable agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the input (none). The description adds no parameter information, which is appropriate here. Baseline for 0 parameters is 4, as no additional parameter semantics are needed.
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 verb ('List') and resource ('all active SSH sessions'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential siblings like 'ssh_connect' or 'ssh_disconnect' beyond the obvious list vs. action distinction.
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 an established SSH connection first), nor does it clarify if this lists only local sessions, remote sessions, or both. No explicit alternatives or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return value (session_id) which is helpful, but doesn't describe authentication requirements, error conditions, session management behavior, or what happens with the 'force_new' parameter. For a security-sensitive connection tool with 8 parameters, this leaves significant behavioral gaps.
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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides crucial behavioral information about the return value. No wasted words or unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex SSH connection tool with 8 parameters and no annotations or output schema, the description provides basic purpose and return value information but lacks details about authentication flows, error handling, session lifecycle, or integration with sibling tools. It's minimally adequate but leaves significant contextual gaps for proper tool selection and usage.
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 already documents all 8 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.
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 the verb ('Connect to') and resource ('remote SSH server'), specifying exactly what the tool does. It distinguishes itself from siblings like ssh_exec or ssh_disconnect by focusing on establishing the initial connection rather than executing commands or terminating sessions.
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 implies usage context by mentioning 'Returns session_id for subsequent commands,' suggesting this is the first step in an SSH workflow. However, it doesn't explicitly state when to use this versus alternatives like reusing existing sessions or provide clear exclusions for when other tools might be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![remote-ssh-mcp MCP server](https://glama.ai/mcp/servers/code-pumpkin/remote-ssh-mcp/badges/card.svg)](https://glama.ai/mcp/servers/code-pumpkin/remote-ssh-mcp)

Score Badge

Copy to your README.md:

[![remote-ssh-mcp MCP server](https://glama.ai/mcp/servers/code-pumpkin/remote-ssh-mcp/badges/score.svg)](https://glama.ai/mcp/servers/code-pumpkin/remote-ssh-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/code-pumpkin/remote-ssh-mcp'

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