Skip to main content
Glama
Mr-M-tastic

Power Automate MCP

by Mr-M-tastic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Power Automate MCP

No user-submitted related servers found.

    Related Servers

    • power-automate-mcp-server

      user-vik
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      2
      MIT

    • Minerva MCP

      HoussemMak
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      38 npm
      1
      MIT

    • EndpointSecureOps-MCP

      dwsnttdata
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • Alteryx MCP

      thinhdao276
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read, analyze, edit, and create Alteryx workflows, including summarizing workflows, finding tools, editing configurations, updating SQL, managing connections, and building new workflows programmatically.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 18 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources