The MCP server: your data inside AI assistants
Query plants, soiling, faults and tickets from Claude, ChatGPT or Cursor.
The NuraVolt MCP server exposes 12 tools (list plants, soiling forecasts, fault classification, ticket creation and more) to any assistant that speaks the Model Context Protocol. Business plans authenticate with scoped API keys; Enterprise adds an OAuth connector where each user signs in with their own account and access follows their plant permissions.
Two ways to connect
- API keys (Business and Enterprise)
- Organisation-level service credentials with per-key scopes. Generate them under Settings, then MCP API keys. Best for shared automations.
- OAuth connector (Enterprise)
- Add NuraVolt as a connector by URL; each teammate signs in with their own account. Access follows per-user plant permissions and the audit log names the person, not a key.
Every call, read or write, lands in an audit log with duration, arguments and status. Write tools require an idempotency key so retries can never create duplicate tickets.
Set it up
The full setup guide, including Claude Desktop, ChatGPT and Cursor snippets, scope reference and troubleshooting, lives on the MCP setup page.
Frequently asked questions
See also
See this on your own plants
NuraVolt turns your SCADA and BMS data into early fault detection, degradation-aware BESS analytics, and audit-ready reporting. A fixed-scope audit shows you what we’d find on your portfolio.