SolarAssistant Software
Real-time charts, analytics and power management from via a Raspberry pi - the most powerful, cost effective device on the planet.
https://solar-assistant.io/Connect straight to this server’s public endpoint.
https://solar-assistant.io/mcpWe add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.
Last probed Sep 14, 2026 · solar-assistant.io
19tools discovered
Whoami
Check authentication status and get current user info.
Tool Search
Search every tool available to you. Most are not loaded into your tool list, to keep it short, and this is how you find them: it returns the full definition of each match, and "loaded" says whether it is already in your list. Call anything it returns with tool_call. Call with no arguments to see everything.
Tool Call
Call any tool by name, including one that is not loaded in your tool list. Use tool_search to find it first.
Order Show
Look up SolarAssistant order by ID.
Order Search
Search for SolarAssistant orders. Returns up to 10 matching orders. Call with no parameters to list latest orders.
Site Show
Look up SolarAssistant site by ID or name.
Site Search
Search for SolarAssistant sites. Returns up to 10 matching sites. Call with no parameters to list latest sites. The q parameter accepts free text and any additional key:value filters not covered by the named parameters (e.g. last_seen_after:2026-01-01, build_date_after:2026-01-01).
Site Metric Search
Search solar metrics on a site by topic glob pattern. Topic format: {device}_{number}/{metric_name} (e.g. inverter_1/pv_power) Examples: - q: "inverter_1/*pv*" - PV metrics from inverter 1 - q: "inverter_*/*voltage*" - All voltage metrics across all inverters - q: "battery_*/*state*" - State metrics from all batteries - q: "total/*power*" - All power totals - q: "weather/*" - All weather metrics - q: "*" - All metrics (likely hits the 20-result limit) Results are limited to 20 metrics. Use a
Site Metric History
Query historical metric data from a site's InfluxDB. Use action "measurements" to list available measurements. Use action "query" with a measurement name, aggregation, time range, and group_by interval. Examples: - action: "measurements" - List all available measurements - action: "query", measurement: "PV power", ago: "7d", agg: "max", group_by: "1h" - Hourly max PV power over last 7 days - action: "query", measurement: "Battery state of charge", ago: "1d", agg: "mean", group_by: "15m" - 15-m
Site Logs
Get device logs from a site by source. Examples: - source: "app" - Application logs (default) - source: "app_error" - Errors and warnings only - source: "devices" - Device communication logs - source: "mqtt" - MQTT broker logs - source: "network" - Network logs - source: "dmesg" - Kernel messages - source: "events" - The telemetry event log shown on the unit's /events page, newest first. Unlike the other sources, one entry is one whole event: its message followed by its details, so grep selects
Site App Devices
List available devices on a site: serial ports (/dev/ttyUSBx), hidraw devices (/dev/hidrawx), network devices, running brokers, and USB devices.
Site App Config
Show current Solar Assistant configuration on a site: selected inverter/battery drivers and assigned connections.
Site App Status
Show monitoring status on a site: whether monitoring is running, inverter/battery connection state, and last update time.
Device Vendor Search
Search for device vendors. Returns up to 10 matching vendors.
Device Show
Look up device by ID.
Device List
List devices with pagination. Complete listing (no text search) — use device_search for keyword lookups.
Device Search
Search for devices. Returns up to 10 matching devices.
Event Search
Search device events submitted by sites: alarms, notifications, automation actions and system state changes. Returns up to 100 entries (default 20), most recent first. Call with no parameters to list the latest events.
Event Show
Fetch one device event by id, with its structured details and (for admin/support) debug details.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsReal-time charts, analytics and power management from via a Raspberry pi - the most powerful, cost effective device on the planet.
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate SolarAssistant Software? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles probed 19 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
SolarAssistant Software may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
MCPBundles is an independent platform built on the open Model Context Protocol standard. Not affiliated with Anthropic PBC or Claude.