← Explore all mcp servers

ANALYTICS DATABASES / Microsoft

Microsoft Fabric Real-Time Intelligence MCP Server

Runs KQL queries and management commands against Fabric Eventhouse and Azure Data Explorer, and manages Fabric Eventstreams, Activator triggers and Maps, with Azure Identity credentials.

“This server enables AI agents to interact with Fabric RTI services by providing tools through the MCP interface, allowing for seamless data querying, analysis, and streaming capabilities.”

01 / THE REASONING

Why this made the selection.

  • Published in Microsoft's own repository; the README at this commit lists the Eventhouse, Eventstreams, Activator and Map tools by name and documents FABRIC_RTI_ALLOWED_TOOLS to expose only chosen services or tools.
  • The README states the server is not intended as a production HTTP endpoint and that HTTP mode screens bearer-token shape without cryptographic Entra JWT validation, so its trust boundary is written down.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at 3c765f92ca5067be8ad70a4b5c5daf8f20f236d9
  • LICENSE and pyproject.toml at the same commit

Our findings

  • In stdio mode the README says authentication uses DefaultAzureCredential: environment variables, Visual Studio, Azure CLI, Azure PowerShell, Azure Developer CLI, then an interactive browser login.
  • HTTP mode (FABRIC_RTI_TRANSPORT=http) defaults to 127.0.0.1:3000 at /mcp; FABRIC_RTI_HTTP_DEBUG_MODE allows local process credentials and permissive CORS.
  • pyproject.toml names microsoft-fabric-rti-mcp, Python >=3.10, license MIT, with the microsoft-fabric-rti-mcp console script; the LICENSE is MIT, Copyright (c) Microsoft Corporation.

Not established by this review

  • uvx launch
  • Any Kusto query or command
  • Any Eventstream, Activator or Map change
  • HTTP mode

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. The README installs through VS Code (MCP: Add Server, then the PyPI package microsoft-fabric-rti-mcp) or GitHub Copilot CLI (/mcp add), ending in the uvx block shown. It was not run.
  2. Set KUSTO_ALLOW_UNKNOWN_SERVICES=false with KUSTO_KNOWN_SERVICES, and FABRIC_RTI_ALLOWED_TOOLS, to limit which clusters and tools the agent can reach.

Before you start

  • uv
  • An Azure identity with access to the Fabric workspace or Kusto cluster

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "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"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Fabric RTI MCP README ↗Checked

    https://github.com/microsoft/fabric-rti-mcp/blob/3c765f92ca5067be8ad70a4b5c5daf8f20f236d9/README.md

    Supports: Tools, Installation, Configuration, Authentication, HTTP mode, Permissions and data collection

  2. https://github.com/microsoft/fabric-rti-mcp/blob/3c765f92ca5067be8ad70a4b5c5daf8f20f236d9/pyproject.toml

    Supports: Package name, License MIT, Console script

  3. Fabric RTI MCP LICENSE ↗Checked

    https://github.com/microsoft/fabric-rti-mcp/blob/3c765f92ca5067be8ad70a4b5c5daf8f20f236d9/LICENSE

    Supports: MIT License, Copyright (c) Microsoft Corporation

Evidence & Ask