How to Use the MeteoSource MCP in LangChain

Q: How do I set up the MeteoSource MCP Server in LangChain?

Install langchain-mcp-adapters, then define a MultiServerMCPClient pointing to the Vinkius endpoint. Retrieve the tools using client.gettools() and pass them to your LangChain agent constructor.

Q: What happens if LangChain requests weather for coordinates instead of a place name?

Your LangChain agent will use getnearestweatherplace to find the closest monitored location using latitude and longitude. Once it gets the place ID, it can run the forecast tool.

Feed real-time global weather forecasts directly into your LangChain reasoning loops to automate weather-dependent logistics.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MeteoSource MCP to LangChain

Create your Vinkius account to connect MeteoSource 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 MeteoSource with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chain-linked location resolution for LangChain

`search_weather_places` serves as the entry point for resolving raw location strings into structured identifiers within your LangChain runs using this MCP server. Your LangChain agents use this specific tool to translate messy user inputs like "downtown Chicago" into verified MeteoSource place IDs. If the initial query is broad, your LangChain agent can analyze the list of matched locations and pick the exact MeteoSource record. This setup works perfectly with LangChain's state management, allowing you to pass the resolved place ID into other tools in your pipeline to fetch local coordinates or timezone offsets.

Multi-step weather forecasting with LangChain agents

`get_point_forecast` pulls precise weather predictions for any location resolved by your LangChain agent using the MCP protocol. This tool lets your active chains fetch temperature, precipitation, and wind metrics directly during a run. Because LangChain tracks every step in LangSmith, you can audit how your agent handles these MeteoSource forecast payloads. You see exactly what weather values triggered a specific branch in your logic, making it easy to debug decisions.

Active MCP Server status checks in LangChain pipelines

`check_api_status` verifies that the MeteoSource service is active before your LangChain agent attempts to run heavy analytical chains. This tool acts as a circuit breaker inside your custom LangChain ReAct agents. Integrating this check prevents your LangChain runs from failing mid-execution due to MeteoSource API downtime. It keeps your multi-step weather workflows running reliably even when external dependencies experience brief outages.

Setup guide

Set up MeteoSource 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 MeteoSource 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({
    "meteosource-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 MeteoSource 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 MeteoSource. 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 MeteoSource 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 MeteoSource MCP in LangChain

You chain them together by configuring your LangChain agent to output the place ID from `search_weather_places` and feed it directly into the input schema for `get_point_forecast`. LangGraph manages this state transfer automatically.

Yes, you track this using LangSmith observability. It captures the execution duration of every tool call, like `get_point_forecast`, so you can see how much latency the weather queries add to your agent's response time.

Install `langchain-mcp-adapters`, then define a `MultiServerMCPClient` pointing to the Vinkius endpoint. Retrieve the tools using `client.get_tools()` and pass them to your LangChain agent constructor.

Your LangChain agent will use `get_nearest_weather_place` to find the closest monitored location using latitude and longitude. Once it gets the place ID, it can run the forecast tool.

Your coordinates and place IDs are processed inside an ephemeral, zero-trust V8 sandbox running the MCP daemon. Vinkius does not store the location strings or forecast payloads queried by your LangChain agent; they exist only during active execution.

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