How to Use the NCDC Climate Data Online MCP in LangChain

Q: Can LangChain handle the multi-step lookup needed for NCDC Climate Data Online?

Yes, LangChain is built for this. Your agent can chain listlocations to find a region, use liststations to identify active sensors, and then run getclimatedata to pull the records. This entire sequence happens in a single execution loop.

Q: Does this server support daily and monthly historical averages?

Yes. Your agent can query listdataclasses to verify the resolution of the dataset. It can then request daily or monthly summaries using getdataset to match your analysis requirements.

Feed historical NOAA weather records directly into your LangChain reasoning loops with this dedicated MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect NCDC Climate Data Online MCP to LangChain

Create your Vinkius account to connect NCDC Climate Data Online to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup NCDC Climate Data Online with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build multi-step weather chains in LangChain

Stop hardcoding weather API endpoints. This MCP Server lets your agent inspect the available datasets using `list_datasets` and drill down into specific regions using `list_locations`. LangChain handles the tool selection dynamically, passing the output of one step right into the next tool in your chain. Your agent can look up weather stations in a county, then immediately pull historical records using `get_climate_data`. LangSmith tracks every step of the execution so you can see exactly how the agent navigated the NOAA hierarchy.

Resolve complex climate metadata automatically

Finding the right weather station ID is usually a pain. Your LangChain agent can use `list_data_categories` and `list_data_types` to figure out which variables are actually tracked before running its main query. This saves you from empty API returns. By letting the agent self-correct using `get_station` and `get_dataset`, your pipeline gets the exact temperature or precipitation metrics it needs without hardcoded IDs.

Filter local climate classes dynamically

LangChain chains can now filter data granularity on the fly. The agent queries `list_data_classes` to see if hourly or monthly summaries exist for a location before pulling the actual numbers. This keeps your LLM context clean. Instead of dumping massive raw weather feeds, the agent uses `list_location_categories` to target specific cities and only pulls relevant historical blocks.

Setup guide

Set up NCDC Climate Data Online MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes NCDC Climate Data Online tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "ncdc-climate-data-online-1-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent NCDC Climate Data Online transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by NCDC Climate Data Online. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect NCDC Climate Data Online now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about NCDC Climate Data Online MCP in LangChain

You load the tools into your agent using the LangChain MCP adapter. The agent then calls `list_datasets` and `get_climate_data` autonomously to fetch historical weather records. All tool executions are tracked in LangSmith for debugging.

Yes, LangChain is built for this. Your agent can chain `list_locations` to find a region, use `list_stations` to identify active sensors, and then run `get_climate_data` to pull the records. This entire sequence happens in a single execution loop.

Install the required adapters and connect to the Vinkius endpoint. Use the client to get the tools list, then pass them to your agent constructor. Vinkius manages the API keys and hosting for you.

Yes. Your agent can query `list_data_classes` to verify the resolution of the dataset. It can then request daily or monthly summaries using `get_dataset` to match your analysis requirements.

All requests run inside isolated V8 sandboxes that are completely ephemeral. Your historical weather queries and API tokens are never saved or exposed to other users.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript