Releases

Highlights

The OAuth consent screen — the page you see when a service like ChatGPT asks for permission to read your solar data — now lives in the same Nuxt SPA as the rest of the app. Same amber/orange palette, same dark mode, same components. Internally it was a standalone HTML page; now it's a real page on the site.

What's new

Native consent screen

• New /connect/authorize page renders inside the app shell with the same UCard / UButton / dark-mode treatment used everywhere else.
• The page shows the requesting application's name, your account, and the permissions being granted. Authorize redirects back to the client with an access code; Cancel denies the request.
• Approving still goes through Passport server-side — nothing about the OAuth security model changes; only the UI moved.

Better login redirects

• Hitting a server-rendered route (like /oauth/authorize or /horizon) when you're signed out now bounces you to the Nuxt sign-in page with a ?redirect_to= parameter. After you sign in, you're sent right back to where you were going.
• The login form validates the redirect target so only same-origin URLs are honored.

Cleanup

• The temporary Blade fallback consent view added in v1.2.4 is gone — there's only one consent UI now, and it's part of the SPA.

Highlights

First stable release of Solar Tracking Efficiency — a website for residential and commercial solar PV owners to log monthly readings, track production efficiency, and share dashboards publicly.

Features

Authentication & Accounts

• Register with username (lowercase, no accents) and optional email
• Login with username or email
• Email verification via secure token (24 h expiry)
• Password reset by email
• Profile page: update name, username, email, and password
• Avatar upload and removal

Solar Systems

• Create, edit, and delete solar systems
• Configure system size (kWp), panel count and wattage, inverter and battery capacity, installation date
• Set monthly projected generation (Jan–Dec) from your installer's specs
• Sortable, paginated list of all your systems

Monthly Readings

• Log energy generated, consumed, and exported per month
• Automatic calculation of performance ratio, daily average, self-consumption, and grid import
• Bulk CSV import — paste years of historical data in one shot
• Year and month navigation with trend charts

Public Sharing

• Generate a private share link (token-based, no auth required for viewers)
• Public dashboard exposes only technical and production data — no personal identifiers
• Revoke or rotate the link at any time

Privacy & Data Portability (GDPR / LGPD)

• Export my data: download a full JSON file with your profile, systems, and readings
• Delete account: hard-delete with no soft-delete or recovery — fully GDPR/LGPD compliant
• Privacy Policy page

Public Pages

• Marketing landing page with prerendered SSR for SEO
• Full Open Graph and Twitter Card meta tags for social sharing
• Privacy Policy page
• Releases page (this page)
• XML sitemap

Analytics

• Optional self-hosted Umami integration — no cookies, no cross-site tracking, GDPR-safe

Highlights

Solar Tracking Efficiency now ships with an MCP (Model Context Protocol) server, letting you connect AI clients like Claude Code, Claude Desktop, Cursor, and VS Code directly to your solar data. Ask your AI to log this month's readings, summarize the year, or import historical data — without leaving your chat window.

Features

MCP server

• Single HTTP endpoint at /mcp, JSON-RPC 2.0, throttled to 60 requests per minute per token
• Authenticates with personal access tokens carrying the abilities mcp:read and/or mcp:write
• Three layers of protection on every tool call: route middleware, token ability check, and existing ownership policies — your data stays scoped to you

Read tools

• list_solar_systems — every system you own
• get_solar_system — full detail of a single system, including readings
• get_dashboard_summary — yearly totals, daily averages and performance ratio
• list_readings — monthly readings filtered by year and limit

Write tools

• create_reading — log a new monthly reading (period normalized to the first day of the month, duplicates rejected)
• update_reading — partially update any field on a reading
• delete_reading — permanently remove a reading
• import_readings — bulk-import a CSV string (Portuguese or English headers), with mode (upsert/skip/replace) and dry_run for previewing

Personal access tokens

• New MCP Tokens section under your profile (/profile/mcp-tokens)
• Create tokens with granular abilities and optional expiration
• Plain-text token shown only once on creation, with a one-click copy
• Revoke any token at any time — clients lose access on the next call
• Built-in connection tutorial with copy-paste snippets for Claude Code, Claude Desktop, and Cursor / VS Code

Documentation

• New docs/mcp-server.md reference covering architecture, every tool's input/output, and client setup

Highlights

You can now connect ChatGPT to your solar data — the MCP server now speaks OAuth 2.0 in addition to the existing personal access tokens. Same tools, same data; just a new way for clients that don't accept a static token to log in.

Features

OAuth for AI clients

• ChatGPT custom apps work out of the box: paste the server URL, pick OAuth, and approve the connection on the consent screen.
• Discovery + dynamic client registration follow the public MCP / OAuth specs (RFC 8414, RFC 7591), so future MCP-aware clients should also "just work".
• A branded consent screen shows you exactly which application is asking for access before any data is shared.

Two ways to authenticate, one set of tools

• Personal access tokens (existing, unchanged) for clients that prefer pasting a token: Claude Code, Claude Desktop via mcp-remote, Cursor, VS Code.
• OAuth for clients that need it: ChatGPT today, more tomorrow.
• Both flows reach the exact same tools — list/get systems, dashboard summaries, list/create/update/delete/import readings.

Tutorial updates

• The MCP Tokens page (/profile/mcp-tokens) now has a ChatGPT tab that walks you through the OAuth setup.
• Existing Claude Code / Claude Desktop / Cursor tabs are unchanged.

What's new under the hood

• Laravel Passport added alongside Sanctum, with both auth flows reaching /mcp through auth:sanctum,api.
• OAuth scope mcp:use is treated as full read+write access; granular mcp:read / mcp:write abilities still apply for Sanctum tokens.
• Updated docs/mcp-server.md with the dual auth model, discovery endpoints, and ChatGPT setup steps.