Skip to main content
Glama
Sign In
Codex SSH Terminal MCP

Codex SSH Terminal MCP

by NullPointerChef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_bridge

Start a local Web/PTY SSH bridge that requires manual password entry on the HTML page for secure terminal access.

Instructions

Start the local Web/PTY SSH bridge. Passwords must still be entered by the user in the HTML page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
profile_nameNoSaved profile name. If omitted, the default profile is used.
no_auto_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It mentions password entry requirement, but lacks details on destructiveness, authentication needs, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences with no redundancy. Could be more informative without being verbose, but it is concise.

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 output schema and 3 params, the description lacks behavioral details and parameter explanations, making it incomplete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only profile_name described). The description does not add meaning to 'port' or 'no_auto_start', failing to compensate for the gap.

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 uses a specific verb 'Start' and identifies the resource as 'local Web/PTY SSH bridge', clearly indicating the tool's action. It distinguishes from sibling tools like 'stop_bridge'.

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 on when to use this tool versus alternatives like 'start_config_server' or prerequisites. The description only states what it does, not usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools