Your plant data, wherever your AI lives.
Talk to your NuraVolt plants from Claude Desktop, ChatGPT, Cursor, or any MCP-aware assistant. Same 12 tools your operators use inside the platform, now available inside whichever AI your team already opens every morning.
From AI in your product to your product in AI.
Everyone builds AI inside their SaaS these days. That's useful, but it still means your ops lead has to log in, find the right screen, and ask a question in your chat window.
MCP flips it. Your data becomes a tool source that any AI assistant can call. Your team asks the AI they already use, and the answer comes with real NuraVolt data, real timestamps, real citations — not a hallucinated paraphrase of a marketing page.
For asset managers running plants across a portfolio, that's the difference between another dashboard to remember and a colleague they can ping from anywhere.
Rack R-07-14 is running +4.2°C hotter than the block median. Round-trip efficiency dropped 1.8 pts — that's roughly $185k/yr at your current merchant + capacity mix.
No alarm tripped because the rack is still under thermal cutoff — but SoH will drop ~2× the fleet average if this continues. Recommend inspection within 72 hours; draft ticket ready to create.
Three steps, ten minutes end-to-end.
Generate a scoped key
In the dashboard, mint an API key. Pick the scopes it should have — read-only, or full agent with write access to tickets and cleaning schedules.
Paste into your assistant
Add a one-line MCP config to Claude Desktop, ChatGPT, Cursor, or Continue. Restart. NuraVolt shows up as a tool source.
Ask questions
The AI now knows how to fetch your plants, run diagnoses, search your knowledge base, and open tickets — all against real data, with a full audit trail.
12 tools across every asset lifecycle.
The same tools your Copilot uses inside the platform. Scope-controlled so a single key can be read-only, agent-grade, or something in between.
| Tool | Purpose | Scope | Kind |
|---|---|---|---|
| Plants | |||
| nuravolt_list_plants | List every plant this key can see, with asset type, capacity, and location. | plants:read | read |
| Inverters | |||
| nuravolt_list_inverters | List inverters at a plant, with model and rated capacity. | inverters:read | read |
| Soiling | |||
| nuravolt_get_soiling_forecast | 365-day soiling ratio forecast, confidence bounds, cleaning recommendations. | soiling:read | read |
| Faults | |||
| nuravolt_get_inverter_classification | Rule-based diagnosis for one inverter — cause, confidence, ETA, recommended action. | faults:read | read |
| nuravolt_diagnose_inverter | Bedrock-backed 30-day digital-twin analysis. Severity, fault hypothesis, actions. | diagnosis:run | read |
| BESS | |||
| nuravolt_get_bess_revenue | Ancillary services + wholesale revenue breakdown for a BESS plant. | bess:read | read |
| Tickets | |||
| nuravolt_list_tickets | Maintenance tickets with filters — plant, status, priority, limit. | tickets:read | read |
| nuravolt_create_ticket | Create a maintenance ticket (status NEW). Idempotency key required. | tickets:write | write |
| nuravolt_update_ticket_status | Move a ticket forward: NEW → VALIDATED → ASSIGNED → IN_PROGRESS → DONE. | tickets:write | write |
| nuravolt_comment_on_ticket | Add a comment. Attributed to the API key so the timeline shows the AI source. | tickets:write | write |
| Knowledge base | |||
| nuravolt_search_knowledge_base | Semantic search over uploaded manuals, datasheets, runbooks, incident reports. | kb:read | read |
| Cleaning | |||
| nuravolt_approve_cleaning_schedule | Persist a cleaning schedule with dates + economics. Auto-computes ROI + payback. | cleaning:write | write |
Copy, paste, done.
One config block per host. HTTP streaming under the hood, so it works from any MCP-aware client that speaks the current spec.
{
"mcpServers": {
"nuravolt": {
"url": "https://nuravolt.com/api/mcp/mcp",
"headers": {
"Authorization": "Bearer nv_live_YOUR_KEY_HERE"
}
}
}
}Every call, logged. Every write, idempotent. Every key, revocable.
Keys hashed at rest
Raw tokens are shown to you exactly once. Only a SHA-256 hash and a 14-character prefix live in the database, so a database leak can't produce a working credential.
Fine-grained scopes
Ten scopes across read and write. A read-only key can't create tickets. A tickets-only key can't touch cleaning schedules. Every tool declares its required scope in-code.
Idempotent writes
Every write tool requires an idempotency key. Retries return the original result — a flaky network can never create the same ticket twice.
Full audit log
Every call — read or write, success or forbidden — writes a row to McpToolCall with duration, args, status, and (for writes) the row it created. Visible in the dashboard in real time.
Three real questions, three real answers.
“NuraVolt, which plants have the worst soiling forecast next 30 days? Draft me a cleaning schedule.”
“Show me open critical tickets across the fleet, ranked by revenue at risk.”
“Diagnose INV-07-14 at Sapphire Ridge. What's the recommended action?”
Ten minutes from now, your team is asking NuraVolt questions in Claude.
Mint a scoped key, paste the config, restart your AI. If you'd rather walk through it with us first, book a demo.