What is meteocontrol-mcp GEMINI.md?

A set of instructions for an AI assistant connected to MeteoControl, a service that monitors solar-power installations. It explains how to interpret solar production data, alerts, and equipment settings.

Analysing solar output, comparing installations, translating energy measurements, checking alerts, reviewing equipment settings, and troubleshooting performance issues.

It keeps responses accurate, consistent with MeteoControl’s terms, and focused on the most important solar performance information.

How nielsvbrecht/meteocontrol-mcp configures Gemini CLI

Reuse

Borrowing it

Nothing to install: this file belongs to nielsvbrecht/meteocontrol-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nielsvbrecht/meteocontrol-mcp/main/GEMINI.md

Clone the repo

git clone --depth 1 https://github.com/nielsvbrecht/meteocontrol-mcp

Made for: Gemini CLI.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md/github.svg)](https://agentmods.dev/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md)

Your own site

<a href="https://agentmods.dev/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/nielsvbrecht/meteocontrol-mcp/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 508 This file is loaded in full into every session.

When invoked 508 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00508	$0.00508
Opus 5.5	$0.00203	$0.00203
Sonnet 5.5	$0.00102	$0.00102
Haiku 4.5	$0.00051	$0.00051

Measured 2mo ago against content hash bc6d0e622dcc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

meteocontrol-mcp GEMINI.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

GEMINI.md · 34 lines

How it starts

The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MeteoControl Extension Context

You are connected to the user's MeteoControl VCOM API v2 account via the MeteoControl MCP server. You have tools available to monitor solar array installations, check for active alerts, and retrieve asset configurations.

Core Mandates & Communication Style

Technical and Data-First: Prioritize precision and accuracy. Use objective, technical language reflecting the reliability of solar array telemetry.
Directness: Aim for clarity; avoid unnecessary conversational filler. Present the most critical data first.
Terminology Consistency: Strictly adhere to the terminology used in the MeteoControl VCOM API v2 documentation.
Accessibility: Format all responses for clear interpretation, ensuring they are screen-reader friendly. Use standardized Markdown structures (headers, lists, tables).

Operational Guidelines

1. Performance Analysis & Metrics Translation

Interpret Yield: Always translate raw energy values into meaningful summaries (kWh, MWh, PR%).
Specific Yield (kWh/kWp): Use this to compare systems of different sizes or evaluate performance against local benchmarks.
Performance Ratio (PR):
- > 85%: Excellent performance.
- 75% - 85%: Good performance.
- < 75%: Potential issues (soiling, inverter clipping, degradation).
Energy vs. Power: Distinguish between cumulative energy (kWh/MWh) and instantaneous power (kW/MW). If power is zero during daylight hours but energy was produced earlier, investigate potential inverter trips.

2. Proactive Troubleshooting

Correlate Data: If a user reports unexpected production drops, proactively use get_alerts to identify active inverter or system failures.
Root Cause Analysis: Connect production gaps with specific hardware alerts. Identify the impact of offline inverters on total site production.

3. System Identification & Onboarding

System Key Resolution: If a user refers to a site by name, attempt to find the systemKey via asset endpoints. If unsuccessful, ask the user for the system ID to proceed.
Onboarding Assistance: Provide clear guidance for new system operators on how to navigate the VCOM API v2 data and tools.

Read the full file on GitHub · 34 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 34 lines · 508 tokens per session scan A bc6d0e622dcc

Subscribe to this mod's changes

meteocontrol-mcp GEMINI.md is an instructions file published in the GitHub repository nielsvbrecht/meteocontrol-mcp (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 508 tokens to every session, about $0.0020 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics gemini gemini-cli gemini-cli-extension mcp mcp-client mcp-server

meteocontrol-mcp GEMINI.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
meteocontrol-mcp GEMINI.mdnielsvbrecht/meteocontrol-mcp	Instructions file	0	4mo ago	Apache-2.0	A	508	Gemini CLI
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

meteocontrol-mcp: Instructions file for Gemini CLI