| FMRS | 65 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Teams using Microsoft Fabric RTI who want to interact with data via AI agents using natural language.
- Data engineers needing to quickly analyze streaming data and generate KQL queries automatically.
- Developers looking to automate real-time data monitoring and alerts, such as Activator triggers and Eventstream management.
- Analysts needing to visualize geospatial data and interact with Map items.
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Production deployments seeking a stable, GA MCP server (currently in Public Preview).
- Users unfamiliar with Fabric RTI or KQL, as the server relies on existing knowledge to use effectively.
- Organizations that do not wish to expose their data or workspaces to LLMs or third-party clients.
- Use cases requiring advanced security for HTTP mode without additional configuration.
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Access Microsoft Fabric workspaces, including Eventhouse, Eventstreams, Activator, and Map items.
- Execute KQL queries and management commands, including ingesting data and modifying schemas.
- Create, update, and delete Eventstreams and Map items.
- Create Activator triggers and configure email or Teams notifications.
- Authenticate using Azure Identity, which automatically uses environment credentials, Azure CLI, PowerShell, etc.
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - Public Preview: implementation may change significantly prior to General Availability.
- MCP clients can perform destructive operations (e.g., deleting Eventstreams or Maps) if permissions are too broad.
- Sharing data with third-party LLMs or clients may fall outside Fabric's compliance boundary; review carefully.
- HTTP mode may expose endpoints beyond localhost; ensure a security boundary (e.g., Entra authentication) is placed in front.
- Some tools, like kusto_get_shots, require additional configuration (e.g., embedding endpoints and table).
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | VS Code, GitHub Copilot | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 39 | 26 |
|---|