Skip to main content
Glama
ArtiPyHeart

mcp-jumpserver-gui-sucks

by ArtiPyHeart
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-jumpserver-gui-sucks

No user-submitted related servers found.

    Related Servers

    • mcp-ssh

      xiao-linxin
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for SSH connections through JumpServer, supporting persistent sessions, multiple bastions, and hot-reload configuration.
      7
      MIT

    • AT Series MCP Hub

      xwamt
      F
      license
      Not graded
      quality
      B
      maintenance
      Aggregates MCP tools from AT series IDE plugins into a single server, routing calls to plugin bridges for SSH, JumpServer, and more.
      1
      -

    • Codex SSH Terminal MCP

      NullPointerChef
      A
      license
      B
      quality
      C
      maintenance
      Agent-native SSH control plane with a local Web Terminal, human-in-the-loop secret input, keychain-backed profiles, and user-confirmed uploads for Codex, Claude Code, and MCP-compatible coding agents.
      18
      1
      Apache 2.0

    • sshops

      LckAndLove
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, zero-agent SSH operations tool that enables remote command execution, file transfer, and audit logging. It integrates as an MCP server for AI-driven infrastructure management.
      5 npm
      MIT

    • mcp-ssh-gateway

      demon24ru
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that acts as a boundary agent, giving LLMs and automation systems controlled SSH-based access to remote machines for tasks like administration, diagnostics, and security research.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action—asset discovery, token lifecycle, terminal session control, or SFTP operations—and even close pairs like probe vs acquire and send_input vs run_command have clearly separated scopes. No two tools appear interchangeable.

    Naming Consistency4/5

    The jms_ prefix is used uniformly, and most tools follow a clear verb_noun pattern like list_, get_, create_, acquire_, and close_. A few noun-only names such as jms_paths, jms_status, jms_profile, and the two usage_guide tools break the verb convention, but the overall pattern remains predictable.

    Tool Count2/5

    At 37 tools, the set exceeds the practical count threshold and will make agent tool selection heavier than necessary. The many terminal and SFTP operations are individually useful, but some session-control and usage-guide tools could have been consolidated.

    Completeness5/5

    The tool surface covers the full JumpServer workflow for coding agents: environment/profile discovery, asset and access lookup, connection-token lifecycle, managed KoKo terminal operations, and SFTP file handling. Cleanup operations like expire, close, and exit also prevent dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources