MCP N8N Webhook Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| N8N_API_KEY | Yes | Clave de API para autenticación | |
| N8N_INDEX_NAME | No | Nombre del índice por defecto | PROJECT_CONVERSATIONS |
| N8N_WEBHOOK_ID | Yes | ID único del webhook | |
| N8N_WEBHOOK_URL | Yes | URL base del webhook de n8n | |
| N8N_TABLE_CATEGORY | No | Categoría de tabla por defecto | DEVELOPMENT_LOGS |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| n8n_save_dataC | Guardar información en n8n a través de webhook para indexación y almacenamiento |
| n8n_health_checkB | Verificar la conectividad y estado del webhook de n8n |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.