Hacker News AI Tool Server for LLM Agents - n8n Workflow

This n8n template is ideal for:

AI developers building custom LLM agents (e.g., using LangChain or custom orchestrators).
Users who need to expose reliable, structured APIs from internal n8n nodes without manual coding.
Automation specialists looking for pre-built n8n templates for tool calling workflows.
Anyone needing an n8n trigger endpoint specifically for AI integration.

This powerful n8n workflow provides a robust, zero-configuration backend tool server for interacting with Hacker News. Utilizing the specialized Multi-Chain Processor (MCP) architecture, this n8n template allows any connected AI agent to automatically discover and utilize three distinct operations: retrieving all items, getting a specific article, or finding a user profile.

The core value of this n8n workflow is simplicity and reliability. Since the entire logic is built around native n8n node functionality, data extraction and formatting are handled automatically. The workflow leverages the $fromAI() expression, meaning your AI agent simply asks the relevant question, and the n8n trigger and subsequent nodes handle the parsing and execution, making this one of the most efficient n8n templates for AI integration.

The entire process is initiated by the custom n8n trigger designed for AI agents:

1. AI Agent Request: An external LLM agent (e.g., in LangChain or OpenAI Functions) determines that it needs external data and calls the MCP Tool Server endpoint (the unique webhook URL provided by the n8n trigger).


2. MCP Trigger Activation: The Hacker News Tool MCP Server n8n trigger receives the request, including the intended operation (e.g., 'Article' or 'User') and the parameters parsed by the LLM.


3. Dynamic Routing: The MCP system, inherent to this n8n workflow, routes the request to the corresponding Hacker News n8n node configured for that operation.


4. Parameter Injection: Within each Hacker News n8n node, dynamic expressions like ={{ $fromAI('Article_Id', , 'string') }} extract the necessary parameters (like articleId or username) from the AI's payload.


5. Execution and Response: The dedicated Hacker News n8n node executes the query against the API. The results are automatically formatted by the MCP server and returned directly to the calling AI agent, completing the n8n workflow cycle.

To start using this pre-built n8n workflow, follow these steps:

1. Import the n8n Workflow: Copy the provided JSON code and import it directly into your n8n instance via the 'Workflows' menu.


2. No Credentials Needed: Since the Hacker News n8n node does not require authentication, this n8n template is ready to use immediately.


3. Activate the Workflow: Set the n8n workflow to 'Active' to enable the webhook listener.


4. Copy the Tool URL: Click on the 'Hacker News Tool MCP Server' n8n trigger node and copy the webhook URL. This is the endpoint your external AI agent will use to communicate with this n8n tool server.


5. Configure AI Agent: Paste the URL into your LLM agent configuration (e.g., as a custom tool URL in your LangChain or custom RAG setup).

This n8n workflow relies on core nodes essential for AI tooling:

Hacker News Tool MCP Server (MCP Trigger):
Function: Acts as the primary n8n trigger and tool discovery endpoint. It listens for incoming tool requests from AI agents.
Key Configuration: Path is set to hacker-news-tool-mcp. It automatically handles the routing logic to the attached tool nodes.

Get many items (Hacker News n8n node)
Function: Retrieves a list of trending or recent items from Hacker News (Resource: all).
Key Configuration: Parameters like limit and returnAll use the $fromAI() expression to accept inputs defined by the AI agent.

Get an article (Hacker News n8n node)
Function: Fetches details for a single, specific article ID.
Key Configuration: Uses the $fromAI('Article_Id', ...) expression to dynamically pull the required ID directly from the AI agent's parsed request.

Get a user (Hacker News n8n node)
Function: Retrieves details for a specific Hacker News user profile.
Key Configuration: Uses the $fromAI('Username', ...) expression to accept the target username from the AI request.