Power Automate MCP
Related Servers
Alternatives to Power Automate MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an AI assistant to analyze live Power BI Desktop models and files, and to safely apply approved, reversible edits to copies of Power BI files one change at a time.33MIT
- AlicenseAqualityCmaintenanceEnables AI agents to inspect and edit your personal cloud flows through a local MCP server, authenticated with your own Microsoft account and no admin consent.71MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.78 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to administer Microsoft 365 and Azure, including PowerShell-only areas like Exchange, SharePoint, Teams, and Purview, with risk classification and human approval for write operations.75 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform read/write management of Microsoft Intune and Entra ID across devices, apps, users, groups, Conditional Access, Cloud PC, compliance, and reports via Microsoft Graph.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to access and manage SharePoint sites, lists, and files along with Microsoft Graph and Azure Resource Manager resources over stdio, with authenticated access, write previews/confirmations, and file downloads.66 npmMIT
TDQS
Scored across 18 tools
Most tools target distinct resources, but there are overlapping boundaries: setup_wizard and configure_session both handle setup, sync_pull and get_flow both retrieve flow data, and update_flow and sync_push both modify flows. The descriptions help clarify intent, but the overlaps could still cause an agent to select the wrong tool.
The naming is largely consistent, using snake_case with imperative verb_noun patterns like list_flows, get_flow, update_flow, turn_on_flow, and cancel_run. A few names like setup_wizard and sync_pull/sync_push deviate slightly from the dominant pattern, but the style is readable and predictable overall.
With 18 tools, the server sits in the borderline range. The count is justified by the broad Power Automate domain covering setup, connectors, connections, flow lifecycle, and runs, but includes some possible redundancy such as setup_wizard vs configure_session and sync_pull vs get_flow.
The tool surface covers configuration, connectors, flow retrieval/update, enabling/disabling, and run management, but lacks obvious lifecycle operations like create_flow and delete_flow. It also doesn't provide detailed run retrieval, so some workflows will require workarounds.