Power Automate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PA_PORT | No | Override the default port used for the OAuth loopback redirect. | |
| PA_API_BASE | No | Override the default Power Automate API base URL. | |
| PA_CLIENT_ID | No | Override the default Azure client ID used for authentication. | |
| PA_API_VERSION | No | Override the default API version. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_sessionB | Set Power Automate Designer URL; extracts environmentId + flowId; pick assistant |
| setup_wizardB | Guided setup: paste flow URL, confirm login, pick assistant |
| list_connectorsB | List 1000+ live connectors in env (or curated catalog) |
| list_connectionsA | List existing connections (re-used so no connection-reference errors) |
| ensure_connectionA | Check connector exists + has connection; errors clearly if missing/no access |
| add_connector_actionC | Add connector action to local flow (wires connectionReferences) |
| sync_pullB | Pull live flow into local .pa-flow copy |
| validate_flowB | Validate local flow before push |
| sync_pushC | Push local flow live; refresh browser tab to see |
| list_environmentsA | List environments you can access |
| list_flowsB | List flows in current/given environment |
| get_flowA | Get full flow definition JSON |
| update_flowC | Write modified flow definition (refresh browser tab to see) |
| turn_on_flowD | Enable flow |
| turn_off_flowC | Disable flow |
| list_runsC | List flow runs |
| resubmit_runC | Resubmit a run |
| cancel_runC | Cancel a run |
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 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.