Sáltate la instalación. Funcionando en menos de 2 minutos.
Inicia una prueba gratuita en cloud.anythingmcp.com, añade Znuny con un clic y apunta tu cliente de IA (Claude, ChatGPT, Copilot o Cursor) al endpoint MCP generado. Sin Docker, sin git clone, sin experiencia de desarrollo.
Summary
Znuny (the maintained OTRS fork, and the same API as OTOBO): search and read tickets with their articles, open tickets and add articles, over the GenericInterface REST web service on your own instance.
Prueba a pedir
Prompts de ejemplo para Znuny
Haz clic en un prompt para copiarlo. Pégalo en Claude, ChatGPT, Cursor, Gemini, Copilot u OpenClaw para ejecutarlo contra este conector.
Claude es IA y puede equivocarse. Verifica siempre las respuestas.
💡 ¿Sin instalación? Usa cloud.anythingmcp.com directamente. Inicia sesión, pulsa Connectors → Znuny, pega tus credenciales, genera una MCP API key — listo. Sin Docker, sin
git clone, sin servidor local.
Znuny + ChatGPT
Znuny (the maintained OTRS fork, and the same API as OTOBO): search and read tickets with their articles, open tickets and add articles, over the GenericInterface REST web service on your own instance.
Requisitos previos
Las instrucciones de configuración completas están incluidas en el conector (visibles en el store al seleccionarlo). Las variables de entorno requeridas:
ZNUNY_URL, ZNUNY_WEBSERVICE, ZNUNY_USERNAME, ZNUNY_PASSWORD
Paso 1 — Obtener credenciales
A Znuny web service has to be created before any of this works. Znuny does not expose a REST API by default; you build one in the admin UI.
- Go to Admin → Web Services → Add web service and import Znuny's bundled
GenericTicketConnectorREST.yml(it ships inscripts/examples/webservices/). That file defines exactly the four operations this adapter calls, and the routes below are its routes:GET /Ticketis TicketSearch,POST /Ticketis TicketCreate,GET /Ticket/:TicketIDis TicketGet andPATCH /Ticket/:TicketIDis TicketUpdate. If you wrote your own web service with different routes, change them here to match. - …
Paso 2 — Instalar el adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Paso 3 — Añadir el conector en ChatGPT
ChatGPT soporta servidores MCP a través de la función Connectors (planes Plus / Pro / Team / Enterprise). El plan gratuito no admite conectores personalizados.
- Abre ChatGPT → Settings → Connectors (o pulsa el icono 🔧 en el composer → Manage connectors).
- Pulsa "Add custom connector".
- Rellena:
- Name:
Znuny - MCP server URL:
https://cloud.anythingmcp.com/mcp - Authentication: Bearer token → pega tu MCP API key (de AnythingMCP → Profile → MCP API Keys → New Key)
- Name:
- Pulsa Connect para autorizar.
Herramientas disponibles
| Tool | What it does |
|---|---|
znuny_search_tickets | Search tickets by queue, state, customer or title fragment (TicketSearch) |
znuny_get_ticket | Read one ticket by TicketID (TicketGet) with its queue, state, priority, owner, customer and SLA |
znuny_get_ticket_articles | Read one ticket's full conversation: every article in order with its sender, channel, subject, body and customer visibility |
znuny_create_ticket | Open a real ticket with its first article (TicketCreate) |
znuny_add_article | Add an article to an existing ticket (TicketUpdate) |
znuny_update_ticket | Change a ticket's state, queue, priority or owner (TicketUpdate) — the move that closes a ticket or hands it to another team |
FAQ
¿Funciona el plan gratuito de ChatGPT con los Connectors MCP personalizados? No — se necesita Plus, Pro, Team o Enterprise.
Siguientes pasos
¿Te ha sido útil esta guía?
