How to Use the GridStatus MCP in Cursor

Q: How do I configure the GridStatus MCP Server in Cursor?

Add the server to your .cursor/mcp.json file in your project root. Include your Vinkius API token in the environment arguments under the MCP configuration file, and Cursor will instantly make the grid tools available in Agent mode.

Q: Can Cursor automatically write tests using GridStatus data?

Yes, Cursor queries live endpoints like getlmpdata to fetch actual market prices. It then uses those real-world numbers to write accurate mock assertions and unit tests for your trading logic.

Q: How do I monitor my GridStatus API usage limits inside Cursor?

The editor can run getapiusage to check your remaining query quota. It reads your current row consumption so you do not accidentally hit rate limits while running automated test suites.

Q: Can I run custom database queries against the grid from the editor?

Yes, the agent uses querydataset to execute custom queries. It applies filters and resampling intervals to slice through massive grid datasets before inserting the clean arrays into your code.

Feed live GridStatus power market data directly into Cursor to build and test your energy trading algorithms.

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 Cursor

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Generate trading code using live Cursor MCP Server data

Stop writing energy algorithms with fake placeholder data. When you write code in Cursor, the agent pulls real-time market numbers directly into your active editor files. It calls `get_realtime_lmp` to inject actual five-minute locational marginal prices into your testing scripts, ensuring your model handles real volatility. Cursor reads live GridStatus responses to build precise data structures directly in your open files. If you are writing a parser for CAISO or PJM, Cursor uses the real API payload to generate matching TypeScript interfaces or Python classes on the fly.

Validate grid models with standardized ISO history

Backtesting requires clean historical profiles across different power grids. This MCP tool lets Cursor call `get_standardized_data` to pull uniform hourly load and pricing metrics across regional transmission organizations, generating clean code on the fly. This prevents your code from breaking due to mismatched column names between ERCOT and NYISO. If you need to check schema specifics before generating database migrations, the editor runs `get_dataset_metadata` to inspect columns. You can verify available dates and data frequencies without leaving your active code file.

Track capacity commitments and fuel mixes

Building resource adequacy trackers is simple when your editor has direct grid access. Cursor uses `get_capacity_data` to fetch PJM capacity market commitments and pricing, letting you test how your code handles long-term resource constraints. For carbon accounting tools, the agent queries `get_fuel_mix` to pull live generation breakdowns. It feeds this real-time clean energy percentage directly into your local functions to verify your emission calculations are accurate.

Setup guide

Set up GridStatus MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the GridStatus MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent GridStatus transactions." If the MCP tools are loaded correctly, Cursor will call the GridStatus tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

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

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 Cursor

Add the server to your `.cursor/mcp.json` file in your project root. Include your Vinkius API token in the environment arguments under the MCP configuration file, and Cursor will instantly make the grid tools available in Agent mode.

Yes, Cursor queries live endpoints like `get_lmp_data` to fetch actual market prices. It then uses those real-world numbers to write accurate mock assertions and unit tests for your trading logic.

The editor can run `get_api_usage` to check your remaining query quota. It reads your current row consumption so you do not accidentally hit rate limits while running automated test suites.

Yes, the agent uses `query_dataset` to execute custom queries. It applies filters and resampling intervals to slice through massive grid datasets before inserting the clean arrays into your code.

No. The MCP connector only receives requests for public electricity grid data like load curves and capacity commitments, passing the raw arrays back to your local Cursor instance over a secure local transport.

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