Mcp-Wacta
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WACTA_USER | Yes | The WordPress administrator username. | |
| WACTA_SITE_URL | Yes | The URL of the WordPress site (e.g., https://misitio.com). | |
| WACTA_APP_PASSWORD | Yes | The WordPress application password (e.g., 'xxxx xxxx xxxx xxxx xxxx xxxx'). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wacta_statusA | Radiografía de la suite WaCta: versión del core, qué complementos están activos (Analytics, CRM, Studio, MP), cuántos CTAs hay registrados y el tope del plan. |
| wacta_get_settingsA | Lee la configuración completa de un plugin de la suite (core, studio, analytics o crm). Devuelve el mismo array saneado que ve el panel. |
| wacta_update_settingsA | Cambia ajustes de un plugin de la suite (semántica PATCH: sólo las claves enviadas). Cada cambio pasa por el MISMO sanitizador que el formulario del panel. Ejemplos de claves — core: activated, defaultMessage, dialCode, localNumber, wingetType, ctaPopupEnabled; studio: defaultTemplate, rotationEnabled, externalMode, numbers; analytics: enabled, tracking_enabled, consent_enabled; crm: auto_capture, notify_on_new_lead, frontend_enabled. |
| wacta_list_ctasA | Lista los CTAs del Registro Único (generador de Studio y adopciones por selector) con el tope del plan. La identidad de cada CTA es su slug. |
| wacta_save_ctaA | Crea o actualiza un CTA del Registro Único por su slug. Campos del core: slug (obligatorio), label, message, selector (adopta botones existentes por CSS), capture (pedir datos antes de abrir WhatsApp), track, active. Con CTA Studio activo admite además los campos visuales (kind=studio: text, preset, size, color, number, agent…). |
| wacta_delete_ctaA | Elimina un CTA del Registro Único por su slug. |
| wacta_analytics_dashboardA | Panel de Analytics & UX en JSON: totales, visitantes, páginas, CTAs por página, CTAs globales por slug (cta_totals), atribución por fuente sobre conversiones (source_conversion), tendencia diaria y consentimiento. |
| wacta_analytics_ctasA | Inventario completo de CTAs observados por Analytics (catálogo con contadores agregados por página). |
| wacta_studio_numbersB | Catálogo de números de WhatsApp de CTA Studio (slug, etiqueta, activo, reparto). |
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 9 tools
Each tool targets a distinct resource/action: suite status, settings read/write, CTA CRUD (list/upsert/delete), analytics dashboard vs. CTA inventory, and studio numbers. The two analytics tools are clearly separated by purpose.
All tools share the wacta_ prefix, but the suffix mixes verb_noun patterns (get_settings, list_ctas) with noun phrases (status, analytics_dashboard, studio_numbers). This is a minor deviation from a purely verb-driven convention.
Nine tools is well-scoped for a suite management server, covering configuration, CTA lifecycle, analytics, and numbers without unnecessary bloat or skimping.
The surface covers suite status, settings management, CTA create/update/delete/list, and analytics reporting. A minor gap is the lack of a dedicated 'get single CTA' endpoint, but list_ctas plus save_cta's upsert behavior mitigate this.