MCP Server Trigger Plus

Inicia el workflow actuando como un servidor MCP. Expone herramientas n8n via MCP y añade los parámetros de ruta al output.

Overview

The MCP Server Trigger Plus node acts as a server endpoint within an n8n workflow, exposing n8n tools via the MCP (Modular Communication Protocol) interface. It listens for incoming HTTP requests on a configurable URL path and triggers the workflow when requests are received. The node supports optional authentication methods to protect the endpoint.

This node is useful in scenarios where you want to integrate external systems or chatbots with n8n workflows by sending HTTP requests to trigger automation. For example, it can be used to receive webhook calls from a chatbot platform, passing dynamic route parameters and request data into the workflow for processing.

Properties

Name Meaning
Authentication Optional method to secure the MCP endpoint. Options: None, Header Auth, Bearer Auth
Path URL path for the MCP endpoint. Supports dynamic parameters using : (e.g., /mcp/:chatbotId). If empty, a unique random path is generated automatically

Output

The node outputs JSON data containing details of the incoming HTTP request:

  • params: An object with dynamic route parameters extracted from the URL path.
  • body: The parsed body of the HTTP request, if present.
  • query: Query string parameters from the URL, if any.
  • headers: HTTP headers sent with the request.

This output allows downstream nodes to access all relevant parts of the incoming request for further processing.

The node does not output binary data.

Dependencies

  • Requires an optional API key credential depending on the selected authentication method:
    • For "Header Auth": an API key credential with a header name and value.
    • For "Bearer Auth": an API token credential.
  • No additional external services are required.
  • The node exposes a webhook URL that must be accessible to the clients sending requests.

Troubleshooting

  • Unauthorized responses: If authentication is enabled but credentials are missing or incorrect, the node returns "Unauthorized". Ensure the correct API key/token is configured and that the client sends the expected header or bearer token.
  • Missing credentials error: Errors like "Credentials ... mal configuradas" indicate misconfiguration of the authentication credentials (missing name, value, or token). Verify credential setup in n8n.
  • No streaming support: Requests with Accept: text/event-stream (SSE) are rejected with a message indicating no streaming support.
  • Session termination: DELETE requests return a fixed response indicating session termination; this is informational and does not affect workflow execution.

Links and References

Discussion