Pvgis Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 26, 2026

Solar yield, irradiation and system sizing - no API key.

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

Local MCP server that gives an assistant solar yield, irradiation and PV system sizing data, reportedly without an API key.

What you can do
  • Provides solar energy data to an assistant: estimated photovoltaic yield, solar irradiation figures and help with system sizing.
  • Runs as a local stdio process started from the npm package pvgis-mcp.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Useful when you want an assistant to look up solar irradiation or estimate PV yield and sizing while planning a solar installation, without setting up an API key.
Requirements
Runs locally as a stdio process, so a Node.js runtime and the npm package pvgis-mcp are needed. No authentication, environment variables or headers are declared; network access is presumably required to fetch solar data, though this is not stated.
Before you install
The server is desktop-only and cannot be run from the web. No tools, README or instructions are published, so what it sends to external services and how it handles location data cannot be verified from the supplied material. Treat yield and sizing figures as estimates, not engineering advice.

Installation

In SourceWeft

  1. Open Pvgis Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.