01 · Limits
API tiers run out fast
API access needs a separately issued key and tier. The lowest tier allows 500 calls a day and 30 a minute, which an agent looping over inverters uses up quickly, so the tier is part of the blueprint.
For PV asset managers running meteocontrol VCOM
A meteocontrol VCOM MCP server that answers from your plants under each user's own VCOM login
A meteocontrol VCOM MCP server gives Claude, ChatGPT or Copilot named tools for plants, performance ratio, alarms, tickets and inverter power. meteocontrol documents the VCOM API v2 in public, with API keys sold by tier. meteocontrol ships no MCP server as of 21 September 2026; a read-only community server exists, and Pexon builds a production one.
What we build
A first meteocontrol VCOM tool list, written as the manifest your IT team signs
Built on what meteocontrol GmbH documents: systems (plants), technical data, inverter, meter, sensor and battery measurements, performance ratio and normalised yield, yield forecasts and satellite irradiance, KPI targets, tickets with outages and yield losses, alarms and CMMS work orders. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# meteocontrol-vcom-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_systems: # -> plants with system key and name
backend: GET /v2/systems
mode: read
get_performance_ratio: # system key, period -> PR and normalised yield
backend: GET /v2/systems/{key}/calculations/abbreviations/PR/measurements
mode: read
list_open_alarms: # severity, system -> open alarms with affected power and losses
backend: GET /v2/alarms
mode: read
list_tickets: # status, priority, system, date range -> tickets
backend: GET /v2/tickets
mode: read
get_inverter_power: # system key, inverter ID, period -> P_AC time series
backend: GET /v2/systems/{key}/inverters/{id}/abbreviations/P_AC/measurements
mode: read
draft_ticket_comment: # ticket ID, text -> proposed comment for a person to confirm before posting
backend: POST /v2/tickets/{id}/comments
mode: propose
audit: every call logged with user, tool, arguments and the meteocontrol VCOM responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 21 September 2026
meteocontrol VCOM at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | VCOM API v2 (REST/JSON, docs public): systems, measurements, calculations, forecasts, tickets, alarms and CMMS work orders; the API key and tier are sold separately, from 500 to 150,000 calls a day · vcom-api-client (PHP client, docs public): official client on GitHub that handles OAuth token retrieval and refresh |
| Authentication | Every request needs an X-API-KEY issued by meteocontrol plus an OAuth 2.0 bearer token from POST /v2/login (password or refresh token grant); Basic auth with VCOM credentials is deprecated. The token endpoint is rate-limited to 10 calls a minute. |
| Vendor MCP server | No vendor server. No official meteocontrol MCP server; a community server, nielsvbrecht/meteocontrol-mcp (Apache-2.0, built for Gemini CLI), wraps read endpoints of the VCOM API v2. |
| Vendor AI assistant | None found. |
| Other connectors | meteocontrol-mcp by nielsvbrecht is an unofficial, read-oriented community MCP server in Node.js for systems, energy data, alerts and asset information. |
meteocontrol GmbH (DE). PV and storage asset managers, O&M providers, project developers and energy traders monitoring utility-scale and commercial plants; meteocontrol states 50 GWp and 75,000 plants monitored.
Why meteocontrol VCOM is hard for agents
Where a meteocontrol VCOM connection needs engineering, not configuration
02 · Codes
Measurements are abbreviation codes
Measurements are addressed by codes such as E_Z_EVU, P_AC, SRAD and PR, per device type. The connector needs a mapping layer so that a plain question lands on the right code.
03 · Scale
Portfolio questions need bulk endpoints
A question across hundreds of plants cannot be answered with one call per device inside the rate limit. Tools use the bulk measurement endpoints and aggregate before answering.
04 · Writes
Tickets, alarms and work orders are writable
The API can comment on tickets, close alarms and change work orders. The connector keeps all of these behind a person's confirmation, and closing an alarm is not on the tool list.
meteocontrol VCOM holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
What the connector answers, and what it will not do
Questions it answers
- Which plants had a performance ratio below target last week?
- Show all open critical alarms across the portfolio with their estimated losses.
- What yield losses were booked on ticket 123, and what was the cause?
What it will not do
- Read more than the asking user may read in VCOM; every call runs under that user's own VCOM login.
- Post a comment, close an alarm or change a work order by itself: the only write tool drafts a ticket comment that a person confirms.
- Replace long-term analysis: multi-year yield studies belong in a data warehouse fed by the bulk endpoints.
When this is the wrong page
If one person wants to try read-only questions from Gemini CLI, the community meteocontrol-mcp server already exists. A built connector is right when several people use Claude, ChatGPT or Copilot under their own VCOM logins, with rate limits, an audit log and a confirmed write path.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your meteocontrol VCOM owners and checks every backend against your release and licence. Week two tests whether a person's own meteocontrol VCOM permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named meteocontrol VCOM administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions meteocontrol VCOM teams ask before the first tool call
Does meteocontrol VCOM have its own MCP server?
Not as of 21 September 2026. meteocontrol ships no official MCP server. A community server, nielsvbrecht/meteocontrol-mcp, wraps read endpoints of the VCOM API v2 for Gemini CLI; it is unofficial and has no write path or per-user audit.
Do we need an extra meteocontrol licence for an AI connector?
Yes. The VCOM API needs an API key issued by meteocontrol, sold in tiers from 500 to 150,000 calls a day. The tier decides how many portfolio-wide questions the assistant can answer, so it is sized in the blueprint.
Can the assistant see data a user is not allowed to see in VCOM?
No. Each call runs with an OAuth token from the asking person's own VCOM login, so VCOM decides which plants and tickets they see. Two users asking the same question can get two different answers, and that is tested before go-live.
What does a meteocontrol VCOM connector cost?
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your meteocontrol VCOM administrator in the room if you like.