n8n-nodes-mcp-trigger-headers

anthony-spruyt/n8n-nodes-mcp-trigger-headers
★ 0 stars TypeScript 💻 Code/Dev Tools Updated today
n8n community node - MCP Server Trigger with HTTP header-to-tool-argument injection (X-MCP-Inject-*)
View on GitHub →

Quick Install

Copy the config for your editor. Some servers may need additional setup — check the README.

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "n8n-nodes-mcp-trigge": {
      "command": "npx",
      "args": [
        "-y",
        "anthony-spruyt/n8n-nodes-mcp-trigger-headers"
      ]
    }
  }
}

README Excerpt

n8n community node that extends the built-in MCP Server Trigger to expose HTTP request headers in workflow data. The stock MCP Server Trigger node isolates tool execution from the HTTP transport layer. Headers sent by the MCP client are not accessible in downstream workflow nodes. This means values like `job_id` or `session_token` must be passed as tool arguments via `$fromAI()`, which lets the LLM fabricate them.