What types of datasets are available?

PG&E Data Portals offers: energy usage (electricity and gas by ZIP code), EV adoption (vehicle registrations), solar generation (capacity and production), energy efficiency programs (participation and savings), and grid infrastructure (distribution circuits, substations). Use search_datasets to discover all available datasets.

Is authentication required?

No, the PG&E Data Portals API is publicly accessible without authentication. An API key is optional and only needed if you want higher rate limits for production use. Most queries work out of the box without any credentials.

Can I filter data by specific ZIP codes and date ranges?

Yes! Most tools support zip_code, start_date, and end_date parameters. For example, query_energy_usage accepts ZIP code and date range to return electricity consumption for that specific area and period. Use query_by_date_range for any dataset with custom date filtering.

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

Name: PG&E Data Portals
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to PG&E Data Portals through Vinkius, pass the Edge URL in the `mcps` parameter and every PG&E Data Portals 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 Data Portals Specialist",
    goal="Help users interact with PG&E Data Portals effectively",
    backstory=(
        "You are an expert at leveraging PG&E Data Portals 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 Data Portals "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 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.

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

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 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 Data Portals to CrewAI via MCP

Follow these steps to integrate the PG&E Data Portals 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 10 tools from PG&E Data Portals

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

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with PG&E Data Portals 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 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 Data Portals + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries PG&E Data Portals 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 Data Portals, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain PG&E Data Portals 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 Data Portals against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

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

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

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

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

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

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

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

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

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

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

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

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 CrewAI

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

"List all available PG&E datasets."

"Show me electricity usage for ZIP code 94102."

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

Troubleshooting PG&E Data Portals MCP Server with CrewAI

Common issues when connecting PG&E Data Portals 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

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

PG&E Data Portals + CrewAI FAQ

Common questions about integrating PG&E Data Portals 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.