MCP N8N Webhook Server
Manages configuration through environment variables, allowing customization of webhook URLs, API keys, index names, and table categories for the n8n integration.
Enables storing structured data through n8n webhooks for saving conversations, project documentation, and development logs, with support for custom indexing and categorization to facilitate later retrieval and searching.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP N8N Webhook Server save this conversation about implementing vector storage to the AI_ML project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP N8N Webhook Server
Servidor MCP (Model Context Protocol) para enviar datos a un webhook de n8n para almacenamiento e indexación.
Descripción
Este servidor MCP permite a los asistentes de IA guardar información estructurada en n8n a través de webhooks. Es ideal para:
Guardar conversaciones y logs de desarrollo
Almacenar documentación de proyectos
Indexar información para búsquedas posteriores
Crear embeddings de contenido para RAG
Related MCP server: MCP Server for n8n Integration
Instalación
npm install
npm run buildConfiguración
Crea un archivo .env basado en config.example.env:
cp config.example.env .envConfigura las variables de entorno:
N8N_WEBHOOK_URL: URL base del webhook de n8nN8N_WEBHOOK_ID: ID único del webhookN8N_API_KEY: Clave de API para autenticaciónN8N_INDEX_NAME: Nombre del índice por defecto (opcional, default: PROJECT_CONVERSATIONS)N8N_TABLE_CATEGORY: Categoría de tabla por defecto (opcional, default: DEVELOPMENT_LOGS)
Uso
Modo desarrollo
npm run devModo inspector (para testing)
npm run inspectorModo producción
npm startHerramientas Disponibles
n8n_save_data
Guarda información estructurada en el webhook de n8n.
Parámetros:
projectName(requerido): Nombre del proyectoprojectCategory(requerido): Categoría del proyectocontentType(requerido): Tipo de contenidotitle(requerido): Título del contenidodescription(requerido): Descripción del contenidotext(requerido): Texto completotags(requerido): Array de etiquetasprojectId(opcional): ID del proyectoprojectStatus(opcional): Estado del proyectolanguage(opcional): Idioma del contenidoindexName(opcional): Nombre del índicetableCategory(opcional): Categoría de tablasource(opcional): Fuente de los datos
n8n_health_check
Verifica la conectividad con el webhook de n8n.
Estructura del Payload
El servidor envía datos en el siguiente formato:
{
"metadata": {
"timestamp": "2025-07-02T10:30:00Z",
"source": "mcp_assistant",
"version": "1.0"
},
"project": {
"id": "proj_001",
"name": "Sistema de Embeddings",
"category": "AI_ML",
"status": "ACTIVE"
},
"content": {
"type": "CONVERSATION",
"title": "Implementación de almacenamiento vectorial",
"description": "Discusión sobre la arquitectura...",
"text": "Se está implementando un sistema...",
"tags": ["embeddings", "vectorial", "conversaciones"],
"language": "es"
},
"indexing": {
"index_name": "PROJECT_CONVERSATIONS",
"table_category": "DEVELOPMENT_LOGS"
}
}Licencia
MIT
Available Tools
2 toolsn8n_health_checkB
Verificar la conectividad y estado del webhook de n8n
Inputs: no named parameters.
n8n_save_dataC
Guardar información en n8n a través de webhook para indexación y almacenamiento
Inputs: projectName (required), title (required), text (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one checks connectivity/status, while the other saves data. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools follow a consistent 'n8n_verb_noun' pattern (n8n_health_check, n8n_save_data). This naming convention is uniform and predictable, enhancing readability and usability.
With only two tools, the server feels thin for a webhook server that might require more operations like listing, updating, or deleting data. This limited scope could hinder agent workflows, indicating an under-provisioned tool surface.
The server lacks essential CRUD operations for a webhook domain; it only offers health checks and data saving. Missing tools for retrieving, updating, or managing webhook data create significant gaps that will likely cause agent failures in broader tasks.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Cross-tool persistent memory and context for AI assistants over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with n8n workflows through natural language, supporting actions like listing, creating, updating, executing and monitoring workflows.364 npm1,630MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables AI agents to interact with n8n workflows and automation tools through a standardized interface, allowing execution of workflows and access to n8n functions.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows AI agents to interact with n8n workflows through natural language, enabling workflow management and execution via SSE connections.148 npm7MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for effective workflow automation.2854,168 npm23,234MIT