Freshservice MCP Server
freshservice-mcp
Un servidor MCP (Model Context Protocol) que conecta asistentes de IA a tu instancia de Freshservice ITSM. Gestiona tickets, activos, cambios, problemas, catálogo de servicios, base de conocimientos y más mediante lenguaje natural.
Características
53 herramientas en 9 categorías:
Categoría | Herramientas | Descripción |
Tickets | 9 | Listar, obtener, crear, actualizar, eliminar, responder, añadir notas, conversaciones, buscar |
Activos | 5 | Listar, obtener, crear, actualizar, eliminar |
Personas | 8 | Solicitantes, agentes, grupos, departamentos (listar + obtener) |
Tareas de ticket | 5 | Listar, obtener, crear, actualizar, eliminar subtareas en tickets |
Entradas de tiempo | 4 | Listar, crear, actualizar, eliminar registros de tiempo |
Cambios | 5 | Listar, obtener, crear, actualizar, eliminar solicitudes de cambio |
Problemas | 5 | Listar, obtener, crear, actualizar, eliminar registros de problemas |
Catálogo de servicios | 3 | Explorar elementos del catálogo, obtener detalles, realizar solicitudes de servicio |
Base de conocimientos | 9 | Categorías, carpetas, artículos (CRUD completo) |
Related MCP server: Service Desk Plus MCP Server
Inicio rápido
Requisitos previos
Node.js 18+
Una cuenta de Freshservice con acceso a API
Tu clave de API de Freshservice (Icono de perfil > Configuración de perfil > Clave de API en el panel derecho)
Instalación mediante npx (recomendado)
No se requiere instalación. Configura tu cliente MCP para ejecutar:
{
"mcpServers": {
"freshservice": {
"command": "npx",
"args": ["-y", "freshservice-mcp"],
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Instalación global
npm install -g freshservice-mcpLuego configura tu cliente MCP:
{
"mcpServers": {
"freshservice": {
"command": "freshservice-mcp",
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Instalación desde el código fuente
git clone https://github.com/tannertm0/freshservice-mcp.git
cd freshservice-mcp
npm install{
"mcpServers": {
"freshservice": {
"command": "node",
"args": ["/path/to/freshservice-mcp/src/index.js"],
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Configuración
Variable | Requerido | Descripción |
| Sí | Tu subdominio de Freshservice (ej. |
| Sí | Tu clave de API de Freshservice |
Configuración del cliente MCP
Claude Desktop - Añadir a ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) o %APPDATA%\Claude\claude_desktop_config.json (Windows)
Claude Code - Ejecutar claude mcp add freshservice -- npx -y freshservice-mcp y luego establecer las variables de entorno
Cursor / VS Code - Añadir a tu configuración de MCP siguiendo la documentación de tu editor
Herramientas disponibles
Tickets
Herramienta | Descripción |
| Listar tickets con filtros (estado, prioridad, solicitante, fecha) |
| Obtener detalles completos del ticket |
| Crear un nuevo ticket |
| Actualizar campos del ticket (estado, prioridad, asignación, etc.) |
| Eliminar un ticket (se mueve a la papelera) |
| Enviar una respuesta en un ticket |
| Añadir una nota pública o privada |
| Ver todas las respuestas y notas |
| Filtrar tickets con sintaxis de consulta |
Activos
Herramienta | Descripción |
| Listar todos los activos/CI |
| Obtener detalles del activo con campos personalizados |
| Registrar un nuevo activo |
| Actualizar campos del activo |
| Eliminar un activo |
Personas y organización
Herramienta | Descripción |
| Usuarios finales |
| Personal de soporte |
| Grupos de agentes con miembros |
| Departamentos |
Tareas de ticket
Herramienta | Descripción |
| Listar subtareas en un ticket |
| Obtener detalles de la tarea |
| Añadir una tarea a un ticket |
| Actualizar estado/asignación de la tarea |
| Eliminar una tarea |
Entradas de tiempo
Herramienta | Descripción |
| Ver el tiempo registrado en un ticket |
| Registrar el tiempo empleado |
| Modificar una entrada de tiempo |
| Eliminar una entrada de tiempo |
Cambios
Herramienta | Descripción |
| Listar solicitudes de cambio |
| Obtener detalles del cambio (tipo, riesgo, programación) |
| Crear una solicitud de cambio |
| Actualizar campos del cambio |
| Eliminar un cambio |
Problemas
Herramienta | Descripción |
| Listar registros de problemas |
| Obtener detalles del problema |
| Crear un registro de problema |
| Actualizar campos del problema |
| Eliminar un problema |
Catálogo de servicios
Herramienta | Descripción |
| Explorar servicios disponibles |
| Obtener detalles del servicio y campos requeridos |
| Enviar una solicitud de servicio |
Base de conocimientos
Herramienta | Descripción |
| Explorar categorías de la base de conocimientos |
| Explorar carpetas de la base de conocimientos |
| Leer artículos |
| Escribir un nuevo artículo |
| Editar un artículo |
| Eliminar un artículo |
Ejemplos de prompts
Una vez configurado, puedes pedirle a tu asistente de IA cosas como:
"Muéstrame todos los tickets P1 abiertos"
"Crea un ticket porque la impresora del tercer piso no funciona"
"¿Qué activos están asignados a John Smith?"
"Añade una nota privada al ticket #5678 diciendo que estamos esperando al proveedor"
"Crea una solicitud de cambio para la actualización del firewall programada para el próximo martes"
"Busca en la base de conocimientos instrucciones para configurar la VPN"
"Registra 2 horas en el ticket #1234 para la depuración del problema de red"
"Muéstrame todos los problemas abiertos y sus niveles de impacto"
"Realiza una solicitud de un nuevo portátil desde el catálogo de servicios"
Sintaxis de consulta de búsqueda
La herramienta search_tickets utiliza la sintaxis de consulta de filtro de Freshservice:
"priority:4 AND status:2" - Urgent + Open tickets
"group_id:12345" - Tickets assigned to a specific group
"agent_id:67890" - Tickets assigned to a specific agent
"created_at:>'2024-01-01'" - Tickets created after a dateDesarrollo
git clone https://github.com/tannertm0/freshservice-mcp.git
cd freshservice-mcp
npm install
npm testLicencia
MIT
Available Tools
53 toolsadd_note_to_ticketC
Add a note to a Freshservice ticket
Inputs: ticket_id (required), body (required), private.
create_assetC
Create a new Freshservice asset
Inputs: name (required), asset_type_id (required), description, user_id, +3 more.
create_changeC
Create a new Freshservice change request
Inputs: subject (required), description (required), requester_id (required), priority, +9 more.
create_problemC
Create a new Freshservice problem
Inputs: subject (required), description (required), requester_id (required), priority, +7 more.
create_solution_articleC
Create a new knowledge base article
Inputs: title (required), description (required), folder_id (required), status, +1 more.
create_ticketC
Create a new Freshservice ticket
Inputs: subject (required), description (required), email, requester_id, +10 more.
create_ticket_taskC
Create a new task on a Freshservice ticket
Inputs: ticket_id (required), title (required), description, status, +3 more.
create_time_entryB
Log time spent on a Freshservice ticket
Inputs: ticket_id (required), agent_id (required), time_spent (required), note, +2 more.
delete_assetC
Delete a Freshservice asset
Inputs: display_id (required).
delete_changeC
Delete a Freshservice change request
Inputs: change_id (required).
delete_problemB
Delete a Freshservice problem
Inputs: problem_id (required).
delete_solution_articleC
Delete a knowledge base article
Inputs: article_id (required).
delete_ticketC
Delete a Freshservice ticket (moves to trash)
Inputs: ticket_id (required).
delete_ticket_taskC
Delete a task from a Freshservice ticket
Inputs: ticket_id (required), task_id (required).
delete_time_entryC
Delete a time entry from a Freshservice ticket
Inputs: ticket_id (required), entry_id (required).
get_agentC
Get details of a specific agent
Inputs: agent_id (required).
get_assetC
Get details of a specific asset
Inputs: display_id (required).
get_changeC
Get details of a specific change request
Inputs: change_id (required).
get_departmentB
Get details of a specific department
Inputs: department_id (required).
get_groupB
Get details of a specific agent group
Inputs: group_id (required).
get_problemB
Get details of a specific Freshservice problem
Inputs: problem_id (required).
get_requesterC
Get details of a specific requester
Inputs: requester_id (required).
get_service_catalog_itemC
Get details of a specific service catalog item
Inputs: item_id (required).
get_solution_articleC
Get a knowledge base article with full content
Inputs: article_id (required).
get_solution_categoryC
Get details of a knowledge base category
Inputs: category_id (required).
get_solution_folderC
Get details of a knowledge base folder
Inputs: folder_id (required).
get_ticketB
Get details of a specific Freshservice ticket
Inputs: ticket_id (required).
get_ticket_conversationsB
Get all conversations (replies and notes) for a ticket
Inputs: ticket_id (required).
get_ticket_taskB
Get details of a specific task on a ticket
Inputs: ticket_id (required), task_id (required).
list_agentsC
List Freshservice agents (support staff)
Inputs: page, per_page, email, active.
list_assetsC
List Freshservice assets/configuration items
Inputs: page, per_page.
list_changesC
List Freshservice change requests
Inputs: page, per_page, filter, order_by, +1 more.
list_departmentsC
List Freshservice departments
Inputs: page, per_page.
list_groupsC
List Freshservice agent groups
Inputs: page, per_page.
list_problemsC
List Freshservice problems
Inputs: page, per_page, order_by, order_type.
list_requestersC
List Freshservice requesters (end users)
Inputs: page, per_page, email.
list_service_catalog_itemsC
List items in the Freshservice service catalog
Inputs: page, per_page.
list_solution_articlesC
List articles in a knowledge base folder
Inputs: folder_id (required), page, per_page.
list_solution_categoriesC
List knowledge base categories in Freshservice
Inputs: page, per_page.
list_solution_foldersC
List folders in a knowledge base category
Inputs: category_id (required), page, per_page.
list_ticketsC
List Freshservice tickets with optional filters
Inputs: page, per_page, filter, requester_id, +4 more.
list_ticket_tasksC
List all tasks for a Freshservice ticket
Inputs: ticket_id (required).
list_time_entriesC
List time entries for a Freshservice ticket
Inputs: ticket_id (required).
place_service_requestC
Place a service request from the Freshservice catalog
Inputs: item_id (required), quantity, email, custom_fields.
reply_to_ticketC
Reply to a Freshservice ticket
Inputs: ticket_id (required), body (required), cc_emails, bcc_emails.
search_ticketsC
Search/filter Freshservice tickets using a query string
Inputs: query (required).
update_assetC
Update an existing Freshservice asset
Inputs: display_id (required), name, description, user_id, +3 more.
update_changeC
Update an existing Freshservice change request
Inputs: change_id (required), subject, description, priority, +8 more.
update_problemC
Update an existing Freshservice problem
Inputs: problem_id (required), subject, description, priority, +6 more.
update_solution_articleC
Update an existing knowledge base article
Inputs: article_id (required), title, description, status, +1 more.
update_ticketC
Update an existing Freshservice ticket
Inputs: ticket_id (required), subject, description, priority, +7 more.
update_ticket_taskC
Update a task on a Freshservice ticket
Inputs: ticket_id (required), task_id (required), title, description, +4 more.
update_time_entryC
Update a time entry on a Freshservice ticket
Inputs: ticket_id (required), entry_id (required), time_spent, note, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 53 tools
Most tools have clearly distinct purposes targeting specific resources and actions (e.g., create_ticket vs. update_ticket vs. delete_ticket). However, some potential overlap exists between list_tickets and search_tickets, and between get_ticket and get_ticket_conversations, which could cause minor confusion for agents about which to use in certain scenarios.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_ticket, list_agents, get_asset, update_problem, delete_change). All tools use snake_case with clear, predictable naming conventions, making them easily readable and systematic.
With 53 tools, the count is excessively high for a single server, likely overwhelming for agents to navigate efficiently. While Freshservice is a comprehensive ITSM platform, this many tools suggests over-fragmentation of operations that could be consolidated or scoped more narrowly.
The tool set provides complete CRUD/lifecycle coverage across all key Freshservice domains (tickets, assets, changes, problems, solutions, agents, requesters, etc.). It includes all essential operations from listing and getting to creating, updating, and deleting, with no obvious gaps for core workflows.
Maintenance
Related MCP Connectors
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
AI-native ITSM and ESM platform. resolve IT and HR requests inside Slack and Teams.
Search, reply, tag, assign and report on ThriveDesk help desk conversations from your AI assistant.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to interact with Freshservice IT service management platform, allowing automated ticket management, change requests, asset tracking, and solution article operations through natural language commands.MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates with Service Desk Plus Cloud API to enable AI assistants perform CRUD operations on service desk entities, including request management, technician management, and email communication.4-
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with structured access to the Freshdesk customer support platform, including tickets, contacts, companies, agents, groups, knowledge base, and SLA configuration. Features decision-tree navigation and destructive-action guardrails.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI models to perform IT service management operations on Freshservice, including managing tickets, changes, problems, releases, assets, projects, and more through a set of MCP tools.362MIT