Is any authentication required?

No! All PG&E Public Datasets are completely free and accessible without any API key or authentication. Just subscribe and start querying energy data immediately.

What customer segments are available?

PG&E provides data for four customer segments: Residential (homes), Commercial (businesses), Industrial (manufacturing), and Agricultural (farming). Each segment has different consumption patterns and billing structures.

Can I compare multiple ZIP codes?

Yes! Use the compare_regions tool with comma-separated ZIP codes (e.g., "94102,94103,94104"). It returns side-by-side usage data, customer counts, and average bills for each region, making it easy to identify geographic differences in energy consumption.

PG&E Public Datasets MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: PG&E Public Datasets
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to PG&E Public Datasets through the Vinkius — pass the Edge URL in the `mcps` parameter and every PG&E Public Datasets tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="PG&E Public Datasets Specialist",
    goal="Help users interact with PG&E Public Datasets effectively",
    backstory=(
        "You are an expert at leveraging PG&E Public Datasets tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in PG&E Public Datasets "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Public Datasets MCP Server

Access PG&E Public Datasets directly from any AI agent and explore energy consumption, billing trends, efficiency savings, and regional comparisons without any authentication.

When paired with CrewAI, PG&E Public Datasets becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PG&E Public Datasets tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Monthly Usage — Get monthly electricity and gas consumption by ZIP code and customer segment
Customer Segments — View energy usage breakdown across Residential, Commercial, Industrial, and Agricultural sectors
Yearly Trends — Analyze year-over-year energy consumption trends
Electricity by ZIP — Access ZIP code-level electricity consumption data
Gas by ZIP — Access ZIP code-level natural gas consumption data
Billing Data — Retrieve average bills and cost metrics by region
Savings Data — Analyze energy efficiency program savings and cost-effectiveness
Regional Comparisons — Compare energy usage across multiple ZIP codes side-by-side

The PG&E Public Datasets MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI 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 Public Datasets to CrewAI via MCP

Follow these steps to integrate the PG&E Public Datasets MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 8 tools from PG&E Public Datasets

Why Use CrewAI with the PG&E Public Datasets MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PG&E Public Datasets through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

PG&E Public Datasets + CrewAI Use Cases

Practical scenarios where CrewAI combined with the PG&E Public Datasets MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries PG&E Public Datasets for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries PG&E Public Datasets, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain PG&E Public Datasets tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries PG&E Public Datasets against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

PG&E Public Datasets MCP Tools for CrewAI (8)

These 8 tools become available when you connect PG&E Public Datasets to CrewAI via MCP:

compare_regions

Returns side-by-side usage figures (kWh and therms), customer counts, and average bills for each region. Use this to identify regional differences in energy consumption, support geographic targeting for efficiency programs, or compare urban vs. rural usage patterns. ZIP codes are comma-separated (e.g., "94102,94103,94104"). Optional dataType and year filters. Compare energy usage data between multiple ZIP codes/regions

get_billing_data

Data is available by ZIP code and customer segment. Use this to analyze energy affordability, compare costs across regions, or identify rate impact on customers. Optional zipCode and year filters. Get billing data and average costs from PG&E public datasets

get_electricity_by_zip

Returns monthly or annual usage figures broken down by geographic area. Use this to compare electricity usage across neighborhoods, identify high-consumption areas, or support energy efficiency targeting. Optional year filter. Get electricity consumption data for specific ZIP codes in PG&E service area

get_gas_by_zip

Returns monthly or annual gas usage figures by geographic area. Use this to analyze heating demand patterns, compare gas usage across regions, or identify electrification opportunities. Optional year filter. Get natural gas consumption data for specific ZIP codes in PG&E service area

get_monthly_usage

Data is organized by ZIP code, month, year, and customer segment (Residential, Commercial, Industrial, Agricultural). Returns kWh for electric and therms for gas. Use this to analyze consumption patterns over time. Optional filters: dataType ("electric" or "gas"), customerType, zipCode (5-digit), and year (YYYY). Get monthly energy consumption data by ZIP code and customer segment from PG&E public datasets

get_savings_data

Includes program participation counts, kWh/therms saved, program costs, and cost-effectiveness metrics by program type. Use this to evaluate program ROI, compare effectiveness across initiatives, or identify high-impact efficiency strategies. Optional programType and year filters. Get energy efficiency program savings data from PG&E

get_usage_by_customer_type

Shows total consumption for Residential, Commercial, Industrial, and Agricultural sectors. Use this to understand the energy consumption distribution across different customer categories. Optional dataType ("electric"/"gas") and year filters. Get energy usage broken down by customer segment (residential, commercial, industrial, agricultural)

get_yearly_trends

Shows how electricity and gas usage has changed over multiple years. Use this to identify long-term patterns, growth/decline in energy demand, and seasonal variations. Optional dataType filter ("electric" or "gas"). Get yearly energy consumption trends from PG&E public data

Example Prompts for PG&E Public Datasets in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with PG&E Public Datasets immediately.

"Show monthly electricity usage by customer type."

"Compare ZIP codes 94102, 94301, and 95054."

"Show yearly energy consumption trends."

Troubleshooting PG&E Public Datasets MCP Server with CrewAI

Common issues when connecting PG&E Public Datasets to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

PG&E Public Datasets + CrewAI FAQ

Common questions about integrating PG&E Public Datasets MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.