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 Cursor 10 tools — connect in under 2 minutes

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

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install PG&E Data Portals and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "pge-data-portals": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

Cursor's Agent mode turns PG&E Data Portals into an in-editor superpower. Ask Cursor to generate code using live data from PG&E Data Portals and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor via MCP

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using PG&E Data Portals

Open Agent mode in chat and ask: "Using PG&E Data Portals, help me...". 10 tools available

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

Cursor AI Code Editor provides unique advantages when paired with PG&E Data Portals through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

PG&E Data Portals + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

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

These 10 tools become available when you connect PG&E Data Portals to Cursor 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 Cursor

Ready-to-use prompts you can give your Cursor 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 Cursor

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

PG&E Data Portals + Cursor FAQ

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

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.