A
licenseA
qualityC
maintenanceAn MCP-compliant server that enables AI assistants like Claude Desktop to access and analyze Intercom support tickets with full conversation history.
4
8
Apache 2.0
vidal-helpdesk-mcp
by vidal-renao
Provides enterprise-grade helpdesk functionality including ticket creation, status tracking, prioritization, SLA monitoring, and reporting.
Serves as the data persistence layer with isolated schema and row-level security, ensuring data sovereignty and compliance with Swiss revDSG standards.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
🇨🇭 Vidal Helpdesk MCP Server
Enterprise-Grade AI-Powered SaaS Infrastructure for Swiss SMEs Model Context Protocol (MCP) implementation for autonomous ticket orchestration, built with Supabase and Anthropic Claude AI under Swiss revDSG standards.
1. Executive Summary
vidal-helpdesk is an AI-Native production-grade infrastructure designed to transform technical support into an autonomous operation. This server allows Claude Desktop to act as a support orchestrator, managing the incident lifecycle directly in natural language.
Built for companies that require absolute data sovereignty, the system uses local stdio transport and a persistence layer in Supabase (preferably Swiss regions like Zurich), ensuring that the data plane remains under the operator's control.
Business Value:
MTTR (Mean Time To Repair): Drastic reduction through automatic triage and instant resolution suggestions.
Data Locality: Native compliance with the Federal Act on Data Protection (revDSG).
Conversational BI: Ability to query infrastructure health metrics using natural language.
Related MCP server: Supabase MCP Server
2. System Architecture
The server implements a Clean Architecture pattern, isolating the transport protocol from the business logic and the data layer.
┌──────────────────────────┐ JSON-RPC ┌──────────────────────────┐
│ Claude Desktop │ ◄────────────────────► │ Vidal MCP Server │
│ (MCP Client) │ stdio │ (Node.ts 20) │
└──────────────────────────┘ └────────────┬─────────────┘
│ service_role
▼
┌───────────────────────────────────────────┐
│ Supabase Postgres Cluster │
│ (Isolated Schema: 'helpdesk' + RLS) │
└──────────────┬────────────────────┬───────┘
│ │
┌──────────────┴──────┐ ┌──────┴───────┐
│ Anthropic API │ │ Audit Log │
│ (Triage & NLU) │ │ (Traceable) │
└─────────────────────┘ └──────────────┘
3. Tool Inventory (Enterprise v1.2.1)ToolCapabilityAccessLogiccreate_ticketAI-Driven TriageWriteClasificación P1-P4 + SLA Calculation.list_ticketsContext AwarenessReadFiltrado avanzado sobre esquema aislado.get_ticket_statusSLA MonitoringReadEvaluación de Breaches en tiempo real.prioritize_incidentRecursive ReasoningWriteAjuste dinámico de criticidad según contexto.suggest_solutionResolution EngineReadSugerencias multilingües (ES/DE/EN).count_ticketsOperational BIReadAgregación de datos y analítica de carga.generate_reportExecutive AuditReadHealth Score de infraestructura y métricas SLA.
4. Engineering Battle — Real Deployment Lessons (Windows)
Documentación de fricciones técnicas resueltas durante el despliegue en entornos Windows 11:
4.1 Claude Sandbox (Microsoft Store)
La versión MSIX corre en un AppContainer. La configuración debe residir en:
%LOCALAPPDATA%\Packages\Anthropic.ClaudeForWindows_...\LocalCache\Roaming\Claude\claude_desktop_config.json
4.2 JSON Path Escaping
Los paths en el config deben usar doble backslash (\\) o forward slash (/) según RFC 8259 para evitar errores de parseo:
"args": ["C:/Users/Vidal/Projects/vidal-helpdesk/dist/index.js"]
4.3 Gestión de Procesos Huérfanos
Al cerrar la ventana, Claude permanece en el tray y mantiene el proceso node vivo. Para aplicar cambios de código, es imperativo matar el proceso manualmente:
Stop-Process -Name "node" -Force
5. Compliance Notes (revDSG / Swiss)
Data Residency: Todo el contenido reside en Supabase. Se recomienda la región eu-central-2 (Zúrich).
AI Disclosure: Las herramientas de IA deben declararse en el aviso de privacidad como "procesamiento automatizado mediante Anthropic".
Audit Trail: Las columnas created_at / updated_at junto con el ai_summary garantizan la trazabilidad exigida por el principio de transparencia.
6. License & Contact
Proprietary — © 2026 Vidal Reñao Lopelo.
Fullstack Developer | AI-Powered SaaS Infrastructure Specialist
Basel, Switzerland · vidal-pro-portfolio.vercel.appThis server cannot be deployed
Maintenance
ActivitySlowing
ResponsivenessMostly unanswered
Related MCP Connectors
AI-native helpdesk hosted in Germany: tickets, replies, KPIs and knowledge base over MCP.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Build and manage AI-native customer support agents from Claude or any MCP client.
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server providing AI assistants with intelligent Supabase database access, featuring dynamic schema discovery, complete user management, and file storage operations.1MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for self-hosted Supabase with RLS-aware PostgreSQL and PostgREST layers, enabling safe database introspection, SQL queries, and PostgREST access via natural language.MIT
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.3412 npmMIT