Skip to main content
Glama
andrewcharlwood

power-automate-mcp

by andrewcharlwood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

    • Flow Studio - Power Automate

      ninihen1
      A
      license
      Not graded
      quality
      D
      maintenance
      Debug, build, and manage Microsoft Power Automate cloud flows with AI agents. Get action-level error details, build flows from natural language, trigger and resubmit runs, and operate across multiple tenants. Requires a Flow Studio MCP subscription — get an API key at https://mcp.flowstudio.app
      33
      MIT

    • Power Automate MCP

      Mr-M-tastic
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to edit Power Automate cloud flows live, including reading/writing flow definitions, managing connectors, and syncing changes, with no admin rights or app registration required.
      18
      1
      MIT

    • Azure AI Foundry MCP Server

      youssef7788
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Azure AI Foundry services through a unified interface for model exploration and deployment, knowledge indexing and search, AI evaluation, and fine-tuning operations. Supports both GitHub token-based model testing and full Azure deployment workflows.
      3
      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

    A3.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct operation: CRUD on flows, enable/disable, listing flows/runs/connections/environments, and triggering. No overlap; get-flow and get-flow-definition serve different granularity needs.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with hyphens (e.g., create-flow, list-connections, run-flow). No mixed conventions or irregular names.

    Tool Count5/5

    15 tools is well-scoped for a Power Automate server, covering flow lifecycle, run inspection, environment/connection queries, and on-demand triggering without unnecessary duplication.

    Completeness4/5

    Covers full CRUD, enable/disable, flow run management, and environment/connection listing. Missing only connection creation (by design) and potentially flow sharing or permissions, but core flow operations are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources