nodes/generated

Interface McpTriggerNodeParameters

Source


interface McpTriggerNodeParameters {
    authentication?:
        | "none"
        | "headerAuth"
        | "bearerAuth"
        | "n8nOAuth2";
    includeUserInOutput?: boolean;
    instructions?: string;
    path?: string;
    requireExecuteAccess?: boolean;
}

Properties§

§readonly authentication?: "none" | "headerAuth" | "bearerAuth" | "n8nOAuth2"

The way to authenticate Default: "none"

§readonly includeUserInOutput?: boolean

Whether to include the calling user's ID, email and name in the trigger output and in the request the connected tools receive Default: true

§readonly instructions?: string

Sent to MCP clients when they connect. Clients that support server instructions typically add them to the model's system prompt — use for guidance that spans multiple tools, such as tool-choice rules or multi-step workflows. Type options: {"rows":4}

§readonly path?: string

The base path for this MCP server

§readonly requireExecuteAccess?: boolean

Whether the triggering user must also have permission to execute the workflow in the project it belongs to Default: true