Skip to main content
Glama
TMYTiMidlY

portal-mcp-server

by TMYTiMidlY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to portal-mcp-server

No user-submitted related servers found.

    Related Servers

    • Agent SSH MCP

      xcdd
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for persistent SSH sessions with tmux integration, port forwarding, and SFTP file writes, built for AI agent workflows.
      MIT

    • mcp-remote-ssh

      faizbawa
      A
      license
      A
      quality
      A
      maintenance
      MCP server giving AI agents full SSH access with persistent sessions, structured command output, SFTP file transfer, and port forwarding.
      18
      11
      MIT

    • ssh-mcp

      slepp
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI agents SSH access to remote machines through your local OpenSSH client, enabling remote command execution, file transfer, persistent shell sessions, and port forwarding.
      17
      169 PyPI
      25
      MIT

    • R-Shell

      MageGojo
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI assistants to securely operate remote servers via persistent SSH sessions, with tools for command execution, file transfer, directory listing, and system monitoring.
      4
      MIT

    • ssh-chat-mcp

      aiplatforms-ru
      A
      license
      A
      quality
      D
      maintenance
      Zero-config SSH/SFTP MCP server that lets an LLM client open temporary SSH/SFTP sessions to remote hosts, run commands, and upload/download files without holding any pre-baked credentials.
      17
      8 npm
      2
      MIT
    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

    A4.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target distinct resources/actions (read, patch, grep, glob, transfer, tunnel, hosts), and the exec family (remote_exec, remote_shell, remote_job, local_exec) is explicitly differentiated with strong usage guidance. There is still inherent overlap in the command-execution cluster, but the descriptions resolve it well.

    Naming Consistency4/5

    Predominantly consistent snake_case, with a 'remote_' prefix on most tools (remote_exec, remote_shell, remote_job, remote_read, etc.). A few tools break the prefix (hosts, inspect, policy_check, local_exec) but remain readable and snake_case throughout.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and each tool earns its place across file, execution, host, tunnel, and policy concerns. No filler or redundant tools.

    Completeness4/5

    The surface covers the remote-management lifecycle well: files (read/patch/grep/glob/transfer), execution (exec/shell/job/local), host registry, tunnels, policy, and introspection. Minor gaps exist — no dedicated file delete/mkdir and no host edit/update — but these are workable via remote_exec.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources