fxray
OfficialRelated Servers
Alternatives to fxray
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-compatible agents to interact with multiple Dataverse environments via the Dataverse Web API, supporting data operations, metadata inspection, solution management, and other Power Platform development tasks using Azure CLI authentication.4413 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage and troubleshoot Power Automate cloud flows, including listing environments, flows, and runs, with optional write capabilities for triggering, enabling, disabling, and deleting flows.36 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables CRUD operations and schema exploration on Microsoft Dataverse databases using service principal authentication. It allows users to query records with OData filters, manage table entries, and retrieve metadata through a standardized MCP interface.-
- AlicenseNot gradedqualityDmaintenanceEnables D365 F\&O development including object creation, modification, deletion, and analysis through the MCP standard.40MIT
- AlicenseAqualityCmaintenanceMCP server that lets AI assistants scaffold, build, register, query, and diagnose Microsoft Dataverse plug-ins directly from conversation, orchestrating Power Platform CLI and Azure CLI.24MIT
- FlicenseNot gradedqualityDmaintenanceAutomates enterprise Power Platform project setup and management via MCP, reducing setup time from weeks to hours through template-based provisioning, Azure DevOps orchestration, and direct API integration.-
TDQS
Scored across 23 tools
Each tool targets a distinct resource and action granularity: environment status, solution lifecycle, canvas app analysis, and Dataverse metadata are cleanly separated. Even similarly named tools like list_controls/get_control and list_tables/describe_table occupy clearly different levels of detail.
The majority of tools follow a verb_noun pattern such as list_solutions, export_solution, and describe_table, but several use noun-first names like canvas_overview, app_checker_results, and solution_components, with outliers like pac_status and whoami. The mix is readable but not a consistent convention.
At 23 tools this falls in the 16-25 range that feels heavy for a single server, even though the broad Power Platform domain justifies much of the surface. It could plausibly be split into separate environment/solution and canvas-app analysis servers.
The tool set covers a complete workflow from environment discovery, solution export/unpack/diff, canvas app deep inspection, Dataverse metadata queries, to pack/import/publish with dry-run safeguards. Export outputs feed directly into the offline analysis tools, so there are no obvious dead ends.