How to Use the Emissions API MCP in LangChain

Q: How do I connect the Emissions API to my LangChain agent?

Install langchain-mcp-adapters and define a MultiServerMCPClient. Pass the HTTP transport URL for the Emissions API server, call client.gettools(), and bind them to your ReAct agent.

Q: Does the agent know which gases the Emissions API supports?

It finds out dynamically. The agent runs getavailableproducts at the start of the chain to read the current database schema before making specific gas queries.

Q: How do I handle spatial data from the Emissions API in LangChain?

Call getgeojsonemissions and pass the returned geometry collections into a custom parser node. The chain converts the bounding boxes into text summaries for the LLM.

Q: What happens to my telemetry data when querying the Emissions API via LangChain?

The getcarbonmonoxide tool processes geographic coordinates and timestamp ranges purely in memory. Vinkius runs the MCP Server in an ephemeral V8 isolate sandbox, meaning your spatial bounding boxes vanish the millisecond the request finishes.

Build modular environmental monitoring pipelines by connecting the Emissions API directly into your LangChain agents.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Emissions API MCP to LangChain

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chain Emissions API Data in LangGraph

Your LangChain agent calls `get_available_products` to confirm which gases are currently tracked in your target region. It grabs the list, parses the available metrics, and instantly passes that context to the next node in your graph. You don't write custom routing logic. The agent then triggers `get_nitrogen_dioxide` to pull the raw pollution numbers and feeds them straight into a reporting chain. LangSmith tracks the exact latency of every MCP tool call, letting you debug slow API responses when pulling heavy atmospheric datasets.

Autonomous Air Quality Auditing

ReAct agents use the `get_carbon_monoxide` tool to investigate industrial zones without human prompting. You give the agent a bounding box, and it decides to fetch the CO levels, evaluate the concentration, and determine if it needs to pull additional data. If the initial read shows a spike, the agent automatically pivots to run `get_ozone` for cross-validation. This MCP integration means your Python script actively hunts for secondary pollution indicators based on the results of its first query.

Route Spatial Data Through Your MCP Server

The `get_geojson_emissions` tool hands off raw spatial coordinates and pollution density metrics directly to your LangChain document loaders. You extract the geometry objects and pipe them into your preferred vector store or mapping utility. When you need to track agricultural runoff, the agent pulls `get_methane` and formats the output into structured JSON for downstream processing. Every step happens inside the chain, turning raw atmospheric telemetry into actionable alerts.

Setup guide

Set up Emissions API 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 Emissions API 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({
    "emissions-api-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 Emissions API 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 Emissions API. 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 Emissions API 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 Emissions API MCP in LangChain

Install `langchain-mcp-adapters` and define a `MultiServerMCPClient`. Pass the HTTP transport URL for the Emissions API server, call `client.get_tools()`, and bind them to your ReAct agent.

Yes. LangSmith logs the exact duration and token usage for every execution of `get_ozone` or `get_methane`. You see exactly how long the MCP Server takes to return the atmospheric data.

It finds out dynamically. The agent runs `get_available_products` at the start of the chain to read the current database schema before making specific gas queries.

Call `get_geojson_emissions` and pass the returned geometry collections into a custom parser node. The chain converts the bounding boxes into text summaries for the LLM.

The `get_carbon_monoxide` tool processes geographic coordinates and timestamp ranges purely in memory. Vinkius runs the MCP Server in an ephemeral V8 isolate sandbox, meaning your spatial bounding boxes vanish the millisecond the request finishes.

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