Hi Glean team,
We’re actively working on integrating Microsoft Fabric Data Agents via MCP with Glean and wanted to submit a feature request for a more first‑class experience.
Right now, we can reach the Fabric MCP endpoint directly and confirm that:
- The Fabric MCP server is reachable and responds correctly via direct HTTP/MCP calls.
initialize returns a modern MCP protocol version (for example, 2025-06-18).- Tools and calls work as expected when tested outside of Glean.
Inside Glean, we’re wiring this up today as a custom MCP server configuration, which works but requires a fair amount of per‑tenant plumbing (manual OAuth setup in Entra, scope configuration, per‑user delegated tokens, etc.).
Request
We’d love to see Microsoft Fabric MCP (Data Agent) supported as an out‑of‑the‑box / native MCP integration in Glean, similar to other first‑class connectors/action sets, ideally with:
- A predefined MCP server template for Fabric Data Agents (URL pattern, expected auth model, and scopes).
- Guided OAuth setup for Entra ID (Power BI/Fabric delegated permissions, .default scope, etc.).
- Clear docs and guardrails for using Fabric via MCP in Glean (patterns, supported hosts, and recommended use cases for Fabric vs other data-access patterns).
Why this would help
- Fabric is becoming our main governed data platform for analytical and cross‑source scenarios.
- Having it as a native MCP option would lower the integration friction, reduce one‑off custom config per customer, and make it easier to standardize “talk to Fabric data” agents in Glean.
- We’d be happy to act as a design/preview customer and share concrete scenarios (Fabric vs Software API vs direct SQL, Data Agent patterns, etc.).
If there’s already an internal FR or roadmap item for “Native Microsoft Fabric MCP integration”, we’d appreciate being attached to it and seeing any public documentation or timelines that you can share.
Thanks in advance — happy to provide config details and repro steps from our current MCP/Fabric work if that’s helpful.
