tigo-mcp-server
An MCP (Model Context Protocol) server that connects to a user’s Tigo Energy solar monitoring account and exposes tools for system configuration, real-time and historical production data, performance/efficiency analysis, system health/alerts, and maintenance recommendations.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Credentials are loaded from environment variables and not hardcoded (good). However, auth is username/password without described scope granularity or token-based controls. TLS usage is not explicitly stated in the README, though typical HTTPS client behavior is likely via the official tigo-python client. No specific logging redaction guarantees or threat-model details beyond general claims are provided.
⚡ Reliability
Best When
You have a Tigo account with API access and want an AI assistant to query your solar monitoring data via MCP/stdio in a local or controlled environment.
Avoid When
You cannot securely manage Tigo credentials, or you require a documented rate-limit/error-code contract and strong idempotency semantics for automated retries.
Use Cases
- • Ask an AI assistant about current solar production and system status
- • Analyze performance over configurable time ranges (e.g., last 7–30 days)
- • Detect underperforming panels using a threshold
- • Review historical production trends at minute/hour/day granularity
- • Surface system alerts and health ratings
- • Get prioritized maintenance recommendations based on performance analysis
Not For
- • Serving as a public, unauthenticated API for third parties
- • Use cases requiring strict uptime/SLA guarantees or production-grade reliability guarantees
- • Workflows needing a documented web/API-first contract beyond MCP tool schemas
Interface
Authentication
Authentication is done by the server using Tigo username/password loaded from environment variables. No user-facing OAuth flow or scope model is described.
Pricing
No pricing information for the MCP server is provided; it appears to be a self-hosted open-source component.
Agent Metadata
Known Gotchas
- ⚠ Tools generally default to using a primary system when system_id is omitted; agents may need to explicitly pass system_id for multi-system setups.
- ⚠ No rate limit behavior is documented; high-frequency calls may risk upstream API throttling.
- ⚠ Error handling is described generally, but specific MCP error formats/codes and retry guidance are not provided in the README.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for tigo-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.