kdeconnect-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KDCONNECT_SOCKET | No | Path to the kcd Unix socket. Defaults to $XDG_RUNTIME_DIR/kcd/kcd.sock | $XDG_RUNTIME_DIR/kcd/kcd.sock |
| KDCONNECT_MCP_CONFIG | No | Path to the configuration YAML file. Defaults to ~/.config/kdeconnect-mcp/config.yaml | ~/.config/kdeconnect-mcp/config.yaml |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Estado del servidor: listener, configuracion de captura/PII y conteos. |
| list_devicesA | Dispositivos moviles vistos por el listener (desde la base de datos). |
| get_activityC | Timeline unificado de actividad ya redactada. kind: 'sms', 'call' o 'notification' (None = todo). app: filtro parcial por nombre de app (ej. 'whatsapp'). since_minutes: ventana temporal hacia atras (0 = sin limite). unread_only: solo eventos no reconocidos. |
| get_eventsA | Consumo incremental por cursor: eventos con id > after_id, en orden de llegada. Devuelve next_after_id para la siguiente llamada (patron de stream/log). Las retiradas de notificacion actualizan la fila y no se reemiten. |
| wait_for_eventsA | Long-poll: espera (hasta timeout_seconds) a que haya eventos con id > after_id. Recomendado para consumo en vivo: guarda next_after_id y vuelvelo a pasar. |
| search_activityC | Busca texto en titulo/cuerpo/app/contacto sobre lo ya redactado. |
| get_conversationC | Hilo de SMS filtrado por telefono (parcial) o nombre de contacto. |
| get_call_logC | Historial de llamadas. only_missed=True para perdidas. |
| list_active_notificationsC | Notificaciones activas en el movil ahora mismo (backend configurado, redactadas). |
| acknowledge_eventsC | Marca eventos como reconocidos, por ids o por antiguedad. |
| get_redaction_statsA | Conteo de redacciones por categoria (otp, card, iban, phone). |
| sync_sms_historyC | Pide al movil las conversaciones cacheadas y las ingesta (redactadas). |
| scan_devicesC | Escanea dispositivos KDE Connect. include_unpaired para emparejar nuevos. |
| request_pairB | Pide emparejar un dispositivo; hay que confirmar en el movil. |
| accept_pairingB | Acepta una solicitud de emparejamiento entrante (el movil la inicio). Requiere backend kcd. |
| reject_pairingC | Rechaza una solicitud de emparejamiento entrante. Requiere backend kcd. |
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 16 tools
Most tools have clearly distinct purposes (pairing, scanning, status, SMS, calls, notifications). The event family (get_activity, get_events, wait_for_events, search_activity, list_active_notifications) overlaps conceptually, but descriptions clarify different consumption modes; a few could be confused by name alone.
All 16 tools follow a consistent verb_noun snake_case pattern (list_devices, get_status, accept_pairing, sync_sms_history). No mixed conventions or vague verbs are present.
16 tools is slightly above the ideal 3-15 range, but each tool addresses a distinct need in the pairing/event/SMS/call lifecycle. The count is justified by the broad scope, though a few could be consolidated.
The surface covers the full pairing workflow, event consumption (timeline, cursor, long-poll, acknowledge), SMS/call history, active notifications, and redaction stats. Missing device detail/forget actions and send commands, but core monitoring workflows are complete.