NSIDC API Wrapper and MCP Server for AI Agents - n8n Workflow

Markdown-formatted:
AI Developers building specialized agents that require direct access to climate and snow/ice data via a robust n8n workflow.
Data Scientists who want to abstract complex NSIDC API queries using Large Language Models (LLMs).
Automation experts seeking advanced n8n templates for building custom tool servers.
Users who need to connect external, public APIs directly into their n8n AI agent architecture.

This specialized n8n workflow transforms the National Snow and Ice Data Center (NSIDC) Web Service Documentation Index API into an accessible, AI-friendly toolset. By leveraging the Multi-Tool Chain Protocol (MCP) functionality within n8n, this automation provides a robust server endpoint that AI agents can query using natural language instructions.

This specific n8n template streamlines data access, allowing agents to perform detailed searches, retrieve facets, and get suggested terms without needing to handle complex HTTP parameter formatting. The core value lies in how this n8n workflow uses the n8n trigger and httpRequestTool n8n node to expose four critical NSIDC endpoints as ready-to-use functions for any connected AI system, dramatically reducing integration complexity.

Markdown-formatted:

1. Trigger Activation (MCP Server): The process begins when an external AI agent (like an LLM) sends a request to the dedicated MCP endpoint, which is generated by the NSIDC Web Service Documentation Index MCP Server n8n trigger.


2. Tool Selection: Based on the AI agent's prompt, the n8n trigger routes the request to one of the four available httpRequestTool n8n node connectors, effectively choosing which NSIDC API endpoint to call.


3. Parameter Extraction: Within the selected HTTP Request Tool n8n node, dynamic expressions ($fromAI()) are used. These expressions automatically extract necessary query parameters (like searchTerms, startDate, or spatial) from the context provided by the AI agent's request.


4. API Execution: The n8n node executes the external HTTP request to the NSIDC API using the dynamically extracted parameters.


5. Response Handling: The response data from the NSIDC API is then passed directly back through the MCP trigger interface, providing the raw results to the originating AI agent for further processing or synthesis. This ensures that the n8n workflow acts purely as a reliable tool router.

Markdown-formatted:

1. Import the n8n workflow JSON: Load this entire JSON file into your running instance of n8n. This creates the full structure, including all n8n node configurations.


2. Activate the n8n workflow: Toggle the workflow status to 'Active'. This enables the MCP Server endpoint.


3. Retrieve the Endpoint URL: Copy the unique Webhook URL generated by the NSIDC Web Service Documentation Index MCP Server n8n trigger node.


4. Connect AI Agent: Configure your external AI agent or LLM framework (e.g., LangChain, custom agents) to use the copied URL as a callable tool. No external credentials are required for the NSIDC API calls themselves within this specific n8n template.


5. Testing: Test the integration by asking your AI agent a question related to NSIDC data, such as "Search for documents regarding Arctic sea ice minimums."

Markdown-formatted:
NSIDC Web Service Documentation Index MCP Server (MCP Trigger n8n node)
Function: Acts as the entry point and server for the AI agent tools. It receives requests and routes them to the correct function exposed by the n8n workflow.
Key Configuration: The path is set to nsidc-web-service-documentation-index-mcp.

Retrieve Search Facets (HTTP Request Tool n8n node)
Function: Calls the NSIDC /Facets endpoint to view facet information corresponding to a search query.
Key Configuration: Query parameters like searchTerms, count, startIndex, and facetFilters are dynamically populated using the $fromAI() expression, ensuring the AI determines the input for this n8n node.

Search Documents (HTTP Request Tool n8n node)
Function: Executes searches against the NSIDC index based on the OpenSearch 1.1 Specification.
Key Configuration: Uses $fromAI() for inputs such as searchTerms, startDate, endDate, and spatial bounding box definitions, allowing the AI to fully specify the search criteria within this robust n8n node.

Get Search Engine Description (HTTP Request Tool n8n node)
Function: Retrieves the description of the NSIDC search engine web interface.
Key Configuration: This n8n node requires no dynamic parameters, returning static description information upon request.

Suggest Search Terms (HTTP Request Tool n8n node)
Function: Provides suggestions for search terms based on a partially typed query.
* Key Configuration: The required parameter q (query) is mapped using a mandatory $fromAI() expression to capture the user's partial input.