mcp-rport
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPORT_API_URL | No | Base URL of the RPort server | https://iot.console.queo.com.co |
| RPORT_API_USER | Yes | RPort username (required) | |
| RPORT_SSH_USER | No | Preferred SSH user (pi or queo) | pi |
| RPORT_API_TOKEN | Yes | RPort API token (required) | |
| RPORT_DEFAULT_ACL | No | Default ACL for tunnels; empty means MCP IP | |
| RPORT_SSH_PASSWORD | No | SSH password for rport_ssh_exec (optional, only in .env) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rport_get_statusA | Estado del servidor RPort (versi�n, clientes conectados, configuraci�n resumida). |
| rport_whoamiA | Usuario RPort autenticado con el token del MCP y grupos a los que pertenece. |
| rport_list_clientsA | Lista clientes RPort (Raspberry Pi y otros). Por defecto pide campos �tiles (estado, hostname, IPs, tags, t�neles). Filtra por nombre, hostname, estado o b�squeda libre. |
| rport_get_clientA | Detalle de un cliente RPort por id. Opcionalmente incluye procesos y puntos de montaje. |
| rport_list_client_groupsA | Lista grupos de clientes definidos en RPort. |
| rport_list_tunnelsA | T�neles activos visibles para el usuario del token (todos los clientes). |
| rport_create_tunnelA | Crea un t�nel inverso en un cliente activo. El puerto local queda en iot.console.queo.com.co. Para SSH usa remote=22 y scheme=ssh. Por defecto restringe ACL a la IP de salida de este MCP. No ejecuta SSH: devuelve el comando a usar. |
| rport_exec_commandA | Ejecuta un comando en el cliente RPort por el canal del agente (sin t�nel SSH). En Linux suele exigir ruta absoluta, p.ej. /usr/bin/docker. No uses pipes ni redirecciones si el cliente tiene el filtro deny por defecto. Devuelve stdout/stderr cuando el job termina. |
| rport_ssh_execA | Crea un t�nel SSH en RPort y ejecuta un comando en la Pi con usuario pi o queo. El password sale de RPORT_SSH_PASSWORD en .env (nunca lo pidas en el chat). Permite pipes y sudo en la shell de la Pi, a diferencia de rport_exec_command. Cierra el t�nel al terminar salvo keep_tunnel=true. |
| rport_delete_tunnelA | Cierra un t�nel activo. Requiere client_id y tunnel_id (el id num�rico o UUID que devolvi� create o list). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
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.
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.
Ten tools is a well-scoped size for an RPort management server. Each tool covers a meaningful capability without unnecessary duplication or excessive granularity.
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.