2,500+ MCP servers ready to use
Vinkius

UtilityAPI MCP Server for Claude Desktop 12 tools β€” connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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 UtilityAPI and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic SetupΒ·json
{
  "mcpServers": {
    "utilityapi": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
UtilityAPI
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 UtilityAPI MCP Server

Connect UtilityAPI to any AI agent and access utility billing history, granular usage intervals, and meter data from over 100 US utility companies β€” including PG&E, Southern California Edison, Con Edison, National Grid, and more β€” through a single unified API.

Claude Desktop is the definitive way to connect UtilityAPI to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Supported Utilities β€” List all 100+ utility companies available through the platform with their codes and data types
  • Customer Authorizations β€” Create and manage authorization forms for customers to securely share their utility data
  • Meter Management β€” List all authorized utility meters (service points) with addresses, fuel types, and collection status
  • Billing History β€” Retrieve complete billing history with costs, usage amounts (kWh/therms), and billing periods
  • Usage Intervals β€” Access granular smart meter interval data (15-min or hourly readings) for detailed energy analysis
  • Historical Collection β€” Activate backfilling of historical utility data for newly authorized meters
  • Combined Meter Data β€” Get both bills and intervals in a single call for comprehensive energy analysis
  • Event Monitoring β€” Monitor webhook events for authorization flows, data collection status, and errors
  • Demo Testing β€” Test authorization forms with simulated residential and commercial scenarios before production
  • Billing Summaries β€” Track API usage costs and billing periods for your UtilityAPI account

The UtilityAPI MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Desktop 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 UtilityAPI to Claude Desktop via MCP

Follow these steps to integrate the UtilityAPI MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings β†’ Developer β†’ Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using UtilityAPI

Look for the πŸ”Œ icon in the chat. your 12 tools are now available

Why Use Claude Desktop with the UtilityAPI MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with UtilityAPI through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

UtilityAPI + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the UtilityAPI MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

UtilityAPI MCP Tools for Claude Desktop (12)

These 12 tools become available when you connect UtilityAPI to Claude Desktop via MCP:

01

activate_historical_collection

Send an array of meter_uids (from list_meters) to begin backfilling historical data. Once activated, the system will start collecting all available historical data for those meters. Use this after a new customer authorization to ensure you get their complete usage history, not just future data. Data collection may take time depending on the utility and data availability. Activate historical data collection for specific utility meters

02

create_auth_form

Returns a form_uid that can be used to redirect customers to the authorization flow. The utilityCode parameter must be a valid utility code (from list_utilities). Optional scenario parameter controls the test mode: "residential" (home customer), "commercial" (business customer), or other utility-specific scenarios. Use this to set up new data sharing agreements with utility customers. Create a new authorization form for customers to share their utility data

03

get_billing_summaries

Includes billing periods, costs, and meter counts for your UtilityAPI subscription. Optional meterId parameter retrieves summary for a specific meter. Use this to track API usage costs and understand billing periods for your UtilityAPI account. Get billing account summaries for UtilityAPI accounting

04

get_bills

Returns utility bills with: start/end dates, total cost (in dollars), energy usage (kWh for electric, therms for gas), utility name, and meter association. The meters parameter is required β€” provide a single meter UID or comma-separated multiple UIDs. Use this to analyze customer spending on utilities, identify high-cost periods, or provide billing insights. Bills are only available for meters that have been authorized and are actively collecting data. Get utility billing history for authorized meters

05

get_events

Events include: new authorization created, meter data available, collection completed, errors, etc. Use this to monitor the status of data collection workflows, debug authorization issues, or build real-time notifications for when customer data becomes available. Get webhook events from UtilityAPI (authorizations, data collection status)

06

get_form_templates

Templates define what information is collected during the customer authorization process. Use this to understand available form configurations before creating custom authorization forms. Each template has a unique ID used when creating new forms. Get authorization form templates used for customer data sharing

07

get_intervals

This is granular consumption data showing energy usage over time intervals (typically 15-minute or hourly readings from smart meters). Each interval includes: start/end timestamp, usage value (kWh or therms), and cost information. The meters parameter is required β€” provide meter UID(s). Use this for detailed energy analysis, identifying peak usage patterns, demand response analysis, or building energy models. This is more granular than bills β€” ideal for time-series analysis. Get detailed usage interval data (hourly/15-min) for authorized meters

08

get_meter_data

This is a convenience tool that combines results from get_bills and get_intervals for one meter. Returns: complete bill history (dates, costs, usage) plus granular interval data (time-series readings). Use this when you need a complete picture of a customer's utility data β€” both the financial (billing) and technical (usage patterns) aspects β€” for comprehensive energy analysis. The meterUid must be a valid meter UID from list_meters. Get combined billing and interval data for a specific meter in one call

09

list_authorizations

Each authorization represents a customer who has granted access to their utility data. Optional referrals parameter filters by a specific referral code (from test submissions). Set includeMeters=true to also return associated meter data with each authorization. Use this to track which customers have authorized data access and get their referral codes for meter queries. List all customer data sharing authorizations

10

list_meters

Each meter represents a specific utility service connection (electricity or gas) at a customer location. Meter data includes: utility name, service address, fuel type (electric/gas), collection status, and the unique meter_uid used for fetching bills and intervals. Optional authorizationId filters meters to a specific customer authorization. Use the meter_uid with get_bills and get_intervals to retrieve usage data. List all authorized utility meters (service points)

11

list_utilities

Each utility includes its name, utility code (used for form submissions), and supported data types. Use this to find the correct utility code when creating authorization forms or querying utility-specific data. Common utilities include: PG&E (Pacific Gas & Electric), SCE (Southern California Edison), Con Edison, National Grid, and many others across the US. List all supported utility companies available through UtilityAPI

12

test_form_submission

Returns a referral_code that can be used to retrieve the test authorization and associated meter data. Use this during development and testing to verify form configurations work correctly before deploying to production. The formId is the uid returned by create_auth_form. The referral_code returned can be used with list_authorizations to retrieve test data. Test an authorization form to simulate customer authorization and get a referral code

Example Prompts for UtilityAPI in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with UtilityAPI immediately.

01

"List all supported utility companies."

02

"Get the billing history for meter 44445555."

03

"Show me the usage intervals for my authorized PG&E meters."

Troubleshooting UtilityAPI MCP Server with Claude Desktop

Common issues when connecting UtilityAPI to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the πŸ”Œ icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

UtilityAPI + Claude Desktop FAQ

Common questions about integrating UtilityAPI MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the πŸ”Œ icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect UtilityAPI to Claude Desktop

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.