Fabric RTI MCP
Microsoft's MCP server for Fabric Real-Time Intelligence: KQL queries, Eventstreams, Activator triggers and maps from an agent.
- 133 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent runs Kusto management commands and deletes Eventstreams and maps with your Azure permissions.
- Queries and data schemas go to the chosen clusters; services outside the known list are allowed by default.
Install
- Works in
Manual install
{
"mcp": {
"servers": {
"fabric-rti-mcp": {
"command": "uvx",
"args": ["microsoft-fabric-rti-mcp"],
"env": {
"KUSTO_SERVICE_URI": "https://help.kusto.windows.net/",
"KUSTO_SERVICE_DEFAULT_DB": "Samples",
"FABRIC_API_BASE": "https://api.fabric.microsoft.com/v1"
}
}
}
}
}Entry for `settings.json`; in `mcp.json` the block sits under `servers`. Requires `uv`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent runs Kusto management commands and deletes Eventstreams and maps with your Azure permissions.
- Queries and data schemas go to the chosen clusters; services outside the known list are allowed by default.
This is third-party code. Review the repository files before installing.
What it does
Fabric RTI MCP gives an agent access to Microsoft Fabric Real-Time Intelligence. `kusto_query` runs KQL in Eventhouse and Azure Data Explorer, `kusto_command` runs management commands and `kusto_show_queryplan` shows a query plan without executing it. Separate tool groups manage Eventstreams (list, create, update, delete and step-by-step definition building), Activator triggers and Map items. Authentication goes through Azure Identity. The repository includes a KQL skill for Copilot that teaches the agent common syntax pitfalls and query templates. The project is in public preview, so the interface may change before general availability.
Who it is for. Analysts and data engineers in Microsoft Fabric who ask an agent about streaming data in plain language and get KQL back.
Good fit when
- The schema of an Eventhouse table is needed along with ten sample rows.
- An agent checks the plan of an expensive KQL query before running it.
- An Eventstream for sensor data is created from a description.
- An email or Teams message goes out on a table condition through Activator.
Not a fit when
- Your data lives outside Fabric and Azure Data Explorer.
- An agent must not run `.drop` and `.alter` management commands on a production cluster.
- Deleting Eventstreams and maps must stay a manual action.
Example request
Show the schema of the StormEvents table in Eventhouse, take 10 rows and check the query plan before a heavy analysis.MCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
KUSTO_SERVICE_URI- Default Kusto cluster URI.
KUSTO_SERVICE_DEFAULT_DB- Default database for Kusto queries.
FABRIC_API_BASE- Base URL of the Microsoft Fabric API.
FABRIC_RTI_ALLOWED_TOOLS- Comma-separated services or tools to expose to the agent.
Limitations
The project is in public preview and the implementation may change significantly before general availability. Access to Fabric or a Kusto cluster through Azure Identity is required. `kusto_command` and the delete tools change data, so restrict the set with `FABRIC_RTI_ALLOWED_TOOLS`. `KUSTO_ALLOW_UNKNOWN_SERVICES` defaults to `true`, so the agent may connect to clusters outside `KUSTO_KNOWN_SERVICES`. Other Real-Time Intelligence items are marked as planned in the README and are not supported yet.
How to disable. Remove the `fabric-rti-mcp` block from `settings.json` or `mcp.json`. Revoke Azure permissions separately if needed.
FAQ
Which environment variables are required?
None: the server starts with demo settings. `KUSTO_SERVICE_URI` and `KUSTO_SERVICE_DEFAULT_DB` set the default cluster and database.
How do I restrict the tool set?
Set `FABRIC_RTI_ALLOWED_TOOLS` to a comma-separated list of service or tool names, for example `kusto,map_get`.
How do I assess an expensive query without running it?
Call `kusto_show_queryplan`: it returns the plan and execution hints without running the query.
What authentication is used?
The server uses Azure Identity, so no API key goes into the config.
What is the KQL skill in the repository?
The `.github/skills/kql/` folder with rules for writing and debugging KQL: common syntax errors, joins, datetime pitfalls and query templates.
Discussion
No questions or reviews yet.
Related
MCP serversMicrosoft plugin for Fabric: warehouses and Lakehouse, Spark, Power BI, Eventhouse, event streams and migrations for Copilot CLI and Claude Code
Managing Fabric pipelines, dataflows and gateways through Azure AD: the official Microsoft server for VS Code
Jitsu MCP configures and debugs data pipelines: destinations, streams, functions, live events and syncs.
MCP server and CLI to drive real Microsoft Excel: Power Query, DAX, VBA, PivotTables and charts
Official Tableau MCP server: the agent finds data sources, sends queries to them and opens dashboards and Pulse metrics
The official Graphlit MCP server: an agent collects material from Slack, GitHub, mail and websites into a knowledge base and searches it
README in short
The server combines Eventhouse (Kusto), Eventstreams, Activator and Map in one MCP. The tool set can be narrowed with an environment variable.