Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas
Modo principiante Desactivado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenúAjustes
Modo principiante Desactivado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch

Zammad MCP

de servosityversión 0.1.13i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.Servosity/zammad-mcp

Instalar

Resumen

Descripción del creador (original en inglés)

Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Búsqueda y memoria de IA
  • Debes completar: ZAMMAD_API_TOKEN, ZAMMAD_URL, ZAMMAD_MCP_HTTP_TOKEN

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: ZAMMAD_API_TOKEN, ZAMMAD_BASE_URL, ZAMMAD_URL, ZAMMAD_MCP_HTTP_TOKEN, ZAMMAD_USER_AGENT, PRINTING_PRESS_CLIENT_PROFILE, ZAMMAD_MCP_READ_ONLY, ZAMMAD_NO_LOCAL_DATA

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Descargar el archivo .mcpb del creador

El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.

Ejecuta esto en tu terminal

Completa los valores vacíos antes de ejecutarlo.

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • ZAMMAD_API_TOKEN secreto obligatorio env
    Set the ZAMMAD_API_TOKEN credential for the Zammad MCP server.
  • ZAMMAD_BASE_URL env
    Explicit full API base, e.g. https://support.example.com/api/v1. Overrides the instance URL above. Leave blank unless your instance serves the API somewhere non-standard.
  • ZAMMAD_URL obligatorio env
    Root URL of your Zammad instance, e.g. https://support.example.com. The CLI appends /api/v1 itself. Without it the CLI points at a placeholder host that is not your instance.
  • ZAMMAD_MCP_HTTP_TOKEN secreto env
    Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
  • ZAMMAD_USER_AGENT env
    Overrides the User-Agent the CLI sends on Zammad requests. Leave blank to use the CLI's own built-in User-Agent.
  • PRINTING_PRESS_CLIENT_PROFILE env
    Binds this MCP server to one tenant-gated client profile. Leave blank to use the default client profile.
  • ZAMMAD_MCP_READ_ONLY env
    Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing call.
  • ZAMMAD_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 9 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Búsqueda y memoria de IAi

  • Más estrellas que el 0% de los otros 5748 servidores de esta categoría
  • Publicado en el registro más recientemente que el 97% de los otros 5748 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 5748 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Zammad MCP?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: ZAMMAD_API_TOKEN, ZAMMAD_URL, ZAMMAD_MCP_HTTP_TOKEN

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.1.13) llegó al registro ayer.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Context7, Codebase Memory, Exa

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Context7

Up-to-date docs for AI agents

de upstashMuy usado↓ 972,7 mil/sem★ 64,2 milActualizado hace 3 días

Computadora o nube
Instalar

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

de DeusDataMuy usado↓ 18 mil/sem★ 48,1 milActualizado hace 22 días

Se ejecuta en tu computadora
Instalar

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

de exa-labsMuy usado★ 5,2 milActualizado hace 2 meses

Se ejecuta en la nube✓ exa.ai
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Zammad + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Zammad

API. Not affiliated with, endorsed by, or sponsored by Zammad GmbH.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a team-management layer (agent load, customer health, aging backlog, escalation triage, churn risk, feedback mining) the Zammad API can't answer in a single call. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

Your AI agentHow to install the Zammad skill
Claude DesktopRun installer, then Settings > Extensions to register zammad-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add zammad-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add zammad-mcp to mcp.json under the servers key, then pick Agent mode.

The ChatGPT desktop app runs zammad-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list. Setup steps: mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Google GeminiGemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion zammad-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set ZAMMAD_CLI_PATH to an existing binary). Details: #331.

Download Zammad MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Zammad release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install zammad@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Zammad Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iex. Then authenticate per the README and run zammad-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh)

The installer drops both zammad-cli (the CLI) and zammad-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

zammad-cli --version
Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/zammad/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update zammad@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/zammad --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/zammad --force

Hermes speaks MCP natively, so it can also use the zammad-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the zammad skill from https://github.com/servosity/msp-skills/tree/main/skills/zammad. The skill defines how its required CLI (zammad-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your Zammad portal):

ZAMMAD_API_TOKEN=<value> zammad-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Question your team keeps askingCommand
Who on support is overloaded right now?zammad-cli agent-load --json
Is each agent's queue growing or shrinking?zammad-cli agent-trend --weeks 4 --json
Which customers are struggling and need attention first?zammad-cli customer-health --at-risk --json
What tickets have been open too long?zammad-cli overdue --days 3 --json
Which customers sound upset and should be escalated?zammad-cli escalate --json
Which accounts are trending toward churn, and why?zammad-cli churn-risk --json
What are customers asking for (features, pricing, compliance)?zammad-cli feedback-scan --bucket pricing --json
Find and read open tickets (scope to a customer with organization_id:N)zammad-cli tickets search --query "state:open" --json
Log a note or search the Knowledge Basezammad-cli ticket note 12345 --body "..." --internal · zammad-cli kb search "restore" --json
Hear about new and changed tickets as they happen, without pollingzammad-cli webhooks listen · zammad-cli events list --since 0 --json
New tickets as they happen (webhooks)

Zammad can call this machine when a ticket is created or updated or an article is added, so nothing has to poll it.

# Once, with a token that has the admin.webhook and admin.trigger permissions

zammad-cli webhooks register --endpoint http://127.0.0.1:8789/zammad --yes

Keep running on the machine Zammad posts to

zammad-cli webhooks listen

Read what arrived; pass the returned cursor as --since next time

zammad-cli events list --since 0 --json

  • register creates one Zammad webhook and one trigger per event (zammad.ticket.created, zammad.ticket.updated, zammad.article.created). It generates the signature secret and stores it beside your API token, readable only by you; ZAMMAD_WEBHOOK_SECRET overrides it. The secret is never printed: webhooks status shows only where it comes from.
  • listen binds to this machine only (127.0.0.1, port 8789) by default and refuses to start without the secret. Every request must carry Zammad's X-Hub-Signature, checked before the body is read; a delivery it has already seen is dropped, and bodies over 1 MiB are refused.
  • The webhook carries IDs only. The listener fetches the ticket through the API and records the event, so customer text never travels in the webhook.
  • Zammad gives up on a delivery after five attempts over about two minutes. Each time listen starts, it first records what changed while it was down. A delivery Zammad gives up on while listen is running but cannot be reached (a network outage) is not recorded.
  • Zammad has to reach the listener. A self-hosted Zammad on the same server works with the default. Zammad on another machine on your LAN needs listen --addr :8789 --tls-cert --tls-key and an https:// endpoint. A Zammad Cloud instance cannot reach a machine on your LAN.
  • Over MCP, events_list reads the recorded events (read-only, no Zammad call). webhooks_register and webhooks_unregister change Zammad only with confirm: true. listen is CLI-only.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Zammad integrations and MCP servers proxy each question into a live API ca

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx