power-automate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POWER_AUTOMATE_ENV | No | Default environment ID for Power Automate flows. Optional, can be set to avoid repeating it in commands. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-environmentsA | List all Power Platform environments you can access (id, display name, isDefault). Use the returned |
| list-flowsC | List cloud flows in an environment (internal name, display name, state, trigger summary). State 'Started' = enabled, 'Stopped' = disabled. |
| get-flowA | Get the full record for one flow, including its workflow |
| get-flow-definitionA | Get just the workflow definition (triggers + actions JSON) for one flow, for inspecting/editing logic without the surrounding metadata. |
| create-flowA | Create a new cloud flow. |
| update-flowA | Update a flow by PATCHing its properties. Provide the FULL desired properties object (displayName, state, connectionReferences, definition) as JSON -- a typical edit is get-flow, tweak properties, send them back here. |
| enable-flowA | Enable (start) a flow so its triggers fire. Sets state to Started. |
| disable-flowB | Disable (stop) a flow so its triggers stop firing. Sets state to Stopped. |
| delete-flowA | Delete a flow permanently. This cannot be undone. |
| list-flow-triggersA | List a flow's triggers (name + type). Use the trigger name with run-flow. |
| run-flowA | Trigger a flow on demand. The trigger name is usually 'manual' (button/instant flows) or 'Recurrence' (scheduled flows) -- use list-flow-triggers if unsure. |
| list-runsA | List recent runs of a flow (status, start/end time, error). Use this as a health probe -- a latest Failed run or a stale newest startTime means the flow has silently died. |
| get-runA | Get the full record for one run, including status and any top-level error. |
| list-run-actionsA | List the per-action results of a run (status + inputsLink/outputsLink SAS URLs). This is the main way to debug a failed run: find the failed action and inspect its inputs/outputs via the SAS links. |
| list-connectionsA | List the connector connections in an environment (id, connector, display name, status). Use these ids to build the connectionReferences for create-flow / update-flow -- e.g. the shared_office365 connection for mail/calendar Graph calls. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
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.
All tools follow a consistent verb_noun pattern with hyphens (e.g., create-flow, list-connections, run-flow). No mixed conventions or irregular names.
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.
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.