The Emporia Energy MCP Server provides a secure way for LLM applications to access your Emporia Energy device data. This MCP server implementation is in BETA and is subject to change moving forwards.
概览
The Emporia Energy MCP Server provides a secure way for LLM applications to access your Emporia Energy device data. This MCP server implementation is in BETA and is subject to change moving forwards. This MCP Server supports multiple transport methods: local stdio (requiring local execution similar to a command line program), legacy Server-Sent Events (SSE), and Streamable HTTP. For remote transports, authentication uses the same bearer tokens as the API. OAuth is also supported for remote transports (see below). This MCP server targets the Emporia Energy customer cloud - it does not support Partner related behavior. Emporia Energy wants to hear any feedback or suggestions you might have related to this tool (or anything else we're working on). Feel free to reach out with any questions/thoughts by emailing [email protected]. To learn more about Emporia Energy and what we're building - feel free to visit our website at www.emporiaenergy.com.
README
以下为原文 README 节选，完整内容请查看原文。
Emporia Energy MCP Server
The Emporia Energy MCP Server provides a secure way for LLM applications to access your Emporia Energy device data. This MCP server implementation is in BETA and is subject to change moving forwards.
This MCP Server supports multiple transport methods: local stdio (requiring local execution similar to a command line program), legacy Server-Sent Events (SSE), and Streamable HTTP. For remote transports, authentication uses the same bearer tokens as the API. OAuth is also supported for remote transports (see Using the Remote MCP below).
This MCP server targets the Emporia Energy customer cloud - it does not support Partner related behavior.
Emporia Energy wants to hear any feedback or suggestions you might have related to this tool (or anything else we’re working on). Feel free to reach out with any questions/thoughts by emailing [email protected].
To learn more about Emporia Energy and what we’re building - feel free to visit our website at www.emporiaenergy.com. We also have a fairly expansive knowledge base about our products and platform available here: help.emporiaenergy.com.
Features
- Secure authentication with automatic token refresh
- Device listing with comprehensive device information, including which site (Home) each device belongs to
- Site listing, with the ability to filter devices by site — a “site” is what the Emporia app calls a Home
- Energy and Power measurement/usage data retrieval with configurable time scales and energy units
- Well-structured API responses with contextual information
- Additional EV Charger-related tools for session/report details
See Feature Status below for additional details on device specific implementation status and what will be coming in the future.
⚠️ Important Notes
- For the BETA implementation of this MCP server, you must have a native-Emporia Energy account. It will not work if you’ve created an Emporia Account using Google or Apple as third-party authentication providers. In the short-term, you can create a new account (with an email/password) and share your Emporia devices to the new account via the Emporia Energy web or mobile app. We expect that a future version of this MCP server program will have additional flexibility for these third-party provider accounts.
- Emporia accounts with many devices associated (> 20) may have issues with short context windows and long API responses. Similarly, requesting high amounts of measurement data can produce excessively large API responses that can cause problems for some clients and context-limited LLMs.
安装
npx @emporiaenergy/emporia-mcp配置
{
"mcpServers": {
"emporia-mcp": {
"command": "npx",
"args": ["@emporiaenergy/emporia-mcp"],
"env": {
"EMPORIA_ACCOUNT": "<YOUR_EMAIL>",
"EMPORIA_PASSWORD": "<YOUR_PASSWORD>"
}
}
}
}