2,500+ MCP servers ready to use
Vinkius

PG&E Data Portals MCP Server for LangChain 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

LangChain is the leading Python framework for composable LLM applications. Connect PG&E Data Portals through Vinkius and LangChain agents can call every tool natively. combine them with retrievers, memory, and output parsers for sophisticated AI pipelines.

Vinkius supports streamable HTTP and SSE.

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

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MultiServerMCPClient({
        "pge-data-portals": {
            "transport": "streamable_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,
        )
        response = await agent.ainvoke({
            "messages": [{
                "role": "user",
                "content": "Using PG&E Data Portals, show me what tools are available.",
            }]
        })
        print(response["messages"][-1].content)

asyncio.run(main())
PG&E Data Portals
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About PG&E Data Portals MCP Server

Connect PG&E Data Portals to any AI agent and programmatically search, discover, and query PG&E's public energy datasets through natural conversation.

LangChain's ecosystem of 500+ components combines seamlessly with PG&E Data Portals through native MCP adapters. Connect 10 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

What you can do

  • Dataset Search — Search the complete PG&E Data Portals catalog for energy-related datasets
  • Energy Usage — Query electricity and gas consumption data by ZIP code and date range
  • EV Adoption — Access electric vehicle registration and adoption trends by geographic area
  • Solar Generation — Retrieve solar energy production and net energy metering (NEM) statistics
  • Energy Efficiency — Analyze program participation, energy savings achieved, and cost-effectiveness
  • Grid Infrastructure — Access distribution circuit, substation, and grid capacity data
  • Date Range Queries — Filter any dataset by specific time periods for trend analysis
  • Dataset Metadata — Get schema information and field descriptions for all datasets

The PG&E Data Portals MCP Server exposes 10 tools through the Vinkius. Connect it to LangChain in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PG&E Data Portals to LangChain via MCP

Follow these steps to integrate the PG&E Data Portals MCP Server with LangChain.

01

Install dependencies

Run pip install langchain langchain-mcp-adapters langgraph langchain-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save the code and run python agent.py

04

Explore tools

The agent discovers 10 tools from PG&E Data Portals via MCP

Why Use LangChain with the PG&E Data Portals MCP Server

LangChain provides unique advantages when paired with PG&E Data Portals through the Model Context Protocol.

01

The largest ecosystem of integrations, chains, and agents. combine PG&E Data Portals MCP tools with 500+ LangChain components

02

Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

03

LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

04

Memory and conversation persistence let agents maintain context across PG&E Data Portals queries for multi-turn workflows

PG&E Data Portals + LangChain Use Cases

Practical scenarios where LangChain combined with the PG&E Data Portals MCP Server delivers measurable value.

01

RAG with live data: combine PG&E Data Portals tool results with vector store retrievals for answers grounded in both real-time and historical data

02

Autonomous research agents: LangChain agents query PG&E Data Portals, synthesize findings, and generate comprehensive research reports

03

Multi-tool orchestration: chain PG&E Data Portals tools with web scrapers, databases, and calculators in a single agent run

04

Production monitoring: use LangSmith to trace every PG&E Data Portals tool call, measure latency, and optimize your agent's performance

PG&E Data Portals MCP Tools for LangChain (10)

These 10 tools become available when you connect PG&E Data Portals to LangChain via MCP:

01

get_dataset_schema

Use this to understand what columns and data types are available before querying. The datasetId is obtained from search_datasets or list_all_datasets. Get the schema/metadata for a specific PG&E dataset

02

list_all_datasets

Each dataset includes name, description, ID, and metadata. Use this as a starting point to explore what data is available from PG&E — includes energy usage, EV adoption, solar generation, energy efficiency programs, and grid infrastructure datasets. List all available datasets in the PG&E Data Portals catalog

03

query_by_date_range

Specify the dataset ID and start/end dates to retrieve records within that time period. Use this for time-series analysis across any dataset type. Dataset ID from search_datasets. Dates in YYYY-MM-DD format. This is useful for year-over-year comparisons and trend analysis. Query any PG&E dataset filtered by a specific date range

04

query_dataset

Optional filters can be passed as key-value pairs to narrow results (e.g., zip_code, year, region). Use this to retrieve actual data records from any dataset in the PG&E Data Portals. Dataset IDs are obtained from search_datasets or list_all_datasets. Query a specific PG&E dataset with optional filters

05

query_energy_efficiency

), and investment amounts. Use this to analyze program effectiveness and ROI of energy efficiency initiatives. Optional programType filters by program category. Year is YYYY format. Query PG&E energy efficiency program data

06

query_energy_usage

Returns electricity usage aggregated by customer segment (residential, commercial, industrial, agricultural). Use this to analyze energy consumption patterns in specific geographic areas over time. ZIP code format: 5-digit (e.g., "94102"). Dates in YYYY-MM-DD format. Query PG&E energy consumption data by ZIP code and date range

07

query_ev_adoption

Use this to analyze EV adoption trends, identify high-adoption areas, and correlate with charging infrastructure. ZIP code is 5-digit format. Year is YYYY format (e.g., "2024"). Query electric vehicle adoption data by ZIP code and year

08

query_grid_infrastructure

Use this to understand grid capacity, identify areas needing upgrades, or analyze reliability metrics. Region filters by geographic area. dataType can filter by specific infrastructure type. Query PG&E grid infrastructure and distribution data

09

query_solar_generation

Use this to analyze solar adoption and production trends. Region can be a county name or service area identifier. Year is YYYY format. Query solar energy generation data by region and year

10

search_datasets

Use this to discover available datasets before querying specific data. Returns dataset names, descriptions, IDs, and metadata. Optional query parameter filters results by keyword. Search the PG&E Data Portals catalog for energy datasets

Example Prompts for PG&E Data Portals in LangChain

Ready-to-use prompts you can give your LangChain agent to start working with PG&E Data Portals immediately.

01

"List all available PG&E datasets."

02

"Show me electricity usage for ZIP code 94102."

03

"Show EV adoption trends by ZIP code for 2024."

Troubleshooting PG&E Data Portals MCP Server with LangChain

Common issues when connecting PG&E Data Portals to LangChain through the Vinkius, and how to resolve them.

01

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

PG&E Data Portals + LangChain FAQ

Common questions about integrating PG&E Data Portals MCP Server with LangChain.

01

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
02

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
03

Can I trace MCP tool calls in LangSmith?

Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.

Connect PG&E Data Portals to LangChain

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.