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
      D
      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
      41 PyPI
      10
      MIT

    • ssh-mcp

      slepp
      A
      license
      A
      quality
      C
      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
      206 PyPI
      23
      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
      6 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.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect: local execution, policy dry-run, session closure, and background jobs. No overlap in functionality exists.

    Naming Consistency5/5

    All tool names use snake_case with a verb_noun pattern (exec, check, close, job), providing a predictable and coherent naming scheme.

    Tool Count2/5

    With only 4 tools, the surface is insufficient for a server focused on remote host management. Core operations like synchronous remote execution and interactive shell are missing, as implied by references in tool descriptions.

    Completeness1/5

    The tool set lacks essential remote execution tools (e.g., remote_exec, remote_shell) that are referenced in the descriptions of existing tools, creating a severely incomplete interface for the server's purpose.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources