Skip to main content
Glama
LuisQueo

mcp-rport

by LuisQueo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-rport

No user-submitted related servers found.

    Related Servers

    • qb-mcp-server

      coevin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query and manage a Qbee-managed device fleet, offering read tools for device status, files, CVEs, and changes, plus confirmation-gated write operations for configuration, file management, membership, and IAM.
      Apache 2.0

    • remote-agent-connector

      ngojclee
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables a Business MCP Hub to manage and interact with remote agent devices through typed MCP tools, including file operations, terminal/SSH execution, skills, and MCP server calls, with WebSocket relay and device registry.
      -

    • termdesk

      konraddzbik
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to list hosts, run commands, and orchestrate fleet automation over SSH, with per-host opt-in and approval-gated actions while keeping credentials secure.
      3
      MIT
    • meshive-mcp by meshive

      meshive-mcpofficial

      meshive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool has a distinct target resource or action: clients, groups, tunnels, status, or command execution. The main overlap is between rport_create_tunnel and rport_ssh_exec, but their descriptions clearly differentiate tunnel-only creation from executing a command over an SSH tunnel.

    Naming Consistency4/5

    Tool names consistently use the rport_ prefix with verb_noun patterns like list_clients, get_client, create_tunnel, and delete_tunnel. Minor deviations are rport_whoami and rport_ssh_exec, but they are still clear and do not break the overall naming scheme.

    Tool Count5/5

    Ten tools is a well-scoped size for an RPort management server. Each tool covers a meaningful capability without unnecessary duplication or excessive granularity.

    Completeness4/5

    The set covers the core RPort workflows: checking status, listing and inspecting clients, viewing groups, managing tunnel lifecycle, and executing commands. Minor gaps exist, such as no group mutation or dedicated tunnel detail endpoint, but agents can accomplish the primary use cases without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources