A Model Context Protocol (MCP) server that provides seamless integration with the Enapter EMS. This server enables AI assistants and other MCP clients to interact with Enapter sites, devices and telemetry data.
The Enapter MCP Server is available as a public hosted service at
https://mcp.enapter.com/mcp. It uses streamable HTTP transport and OAuth 2.0
for authentication.
For specific instructions on how to connect your preferred AI client, please refer to the following guides:
If you prefer to run your own instance, you can self-host the server using Docker:
docker run --rm --name enapter-mcp-server \
-p 8000:8000 \
enapter/mcp-server:v0.11.0The server can be configured using environment variables and command-line arguments.
The server exposes the following tools for interacting with the Enapter EMS:
| Tool | Description |
|---|---|
search_sites |
Search sites with regex filtering (name, timezone) and pagination |
get_site_details |
Get detailed site information with device and active alert statistics |
search_devices |
Filter devices by site, type, and name pattern |
get_device_details |
Get comprehensive device data (connectivity, properties, active alerts) |
read_blueprint_manifest |
Access device blueprint sections (properties, telemetry, alerts) |
get_historical_telemetry |
Retrieve time-series telemetry with configurable granularity |
For issues, questions, or contributions, please:
- Email us at support@enapter.com.
- Open a GitHub Issue.
- Join our Discord server.
- Check our Contributing Guide.
For information about how we handle data, please refer to the Enapter Privacy Policy.
Made with ❤️ by Enapter