How to Use the GridStatus MCP in LlamaIndex

Q: Can LlamaIndex store historical GridStatus data for offline search?

Yes, you can use querydataset to pull historical grid profiles and write them straight to your vector store. This lets your RAG pipeline search past grid events without repeatedly calling the live API.

Q: How does the GridStatus MCP Server handle schema discovery in LlamaIndex?

The server provides listdatasets and getdatasetmetadata to show your agent what columns and date ranges exist. LlamaIndex uses this metadata to construct precise queries without guessing the table schemas.

Q: Can I index PJM capacity market data with LlamaIndex?

Yes, the agent calls getcapacitydata with the PJM identifier to fetch resource adequacy and commitment data. This output is then indexed as text nodes, making long-term grid capacity planning searchable.

Index real-time US grid data into LlamaIndex MCP vector stores to ground your energy RAG applications in live physical metrics.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GridStatus MCP to LlamaIndex

Create your Vinkius account to connect GridStatus to LlamaIndex 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 GridStatus with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index GridStatus MCP Server Outputs for RAG

The GridStatus MCP Server lets your LlamaIndex agent query live grid metrics and index the raw outputs directly into your vector database. By calling `get_load_data` and `get_fuel_mix`, your system converts real-time electricity demand and generation mix into searchable document nodes. This mechanism eliminates hallucinated grid statistics during user queries. Here's the thing: your pipeline searches the freshly indexed API data first, ensuring that answers about California's solar generation or Texas's wind output match the actual physical state of the grid.

Semantic Search on Deep Grid History

This tool integration uses `get_dataset_metadata` and `query_dataset` to retrieve deep historical records across all major US ISOs. LlamaIndex ingests these multi-gigabyte datasets, chunks them, and builds a semantic index that connects historical weather patterns with grid stress events. Your agent uses this indexed knowledge to answer complex analytical questions about past grid behavior. Instead of writing SQL queries, you ask plain-English questions and let LlamaIndex retrieve the exact historical rows.

Ground Financial RAG in LMP Data

The server exposes `get_lmp_data` and `get_realtime_lmp` to feed live Locational Marginal Pricing directly into your agent's context window. LlamaIndex updates its query engine with these 5-minute pricing intervals, allowing your agent to provide accurate financial context for trading decisions. Grounding your queries in active pricing data prevents your model from referencing stale day-ahead forecasts. The agent compares live market prices with historical trends stored in your vector index to identify immediate arbitrage opportunities.

Setup guide

Set up GridStatus MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all GridStatus MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to GridStatus tools.",
)
response = await agent.run("List recent GridStatus data")

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 GridStatus. 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 GridStatus 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 GridStatus MCP in LlamaIndex

Install llama-index-tools-mcp and initialize the basic client with your Vinkius server URL. Wrap the client in McpToolSpec and call to_tool_list_async to expose the 12 grid tools to your FunctionAgent.

Yes, you can use query_dataset to pull historical grid profiles and write them straight to your vector store. This lets your RAG pipeline search past grid events without repeatedly calling the live API.

The server provides list_datasets and get_dataset_metadata to show your agent what columns and date ranges exist. LlamaIndex uses this metadata to construct precise queries without guessing the table schemas.

Yes, the agent calls get_capacity_data with the PJM identifier to fetch resource adequacy and commitment data. This output is then indexed as text nodes, making long-term grid capacity planning searchable.

The server strictly accesses public electricity grid data, including generation fuel mix, regional demand, and wholesale power prices. Your private vector indexes, local documents, and semantic embeddings are never sent to the GridStatus API.

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