Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/power-automate-mcp-server/issues.md or /mcp/power-automate-mcp-server/issues.json, or Pod over MCP.

Reported issues for power-automate-mcp-server

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to power-automate-mcp-server.

Most discussed

Docker/HTTP transport is single-operator only — no per-user isolation until v2 OAuth

Summary

When deployed over the HTTP transport (Docker), this server collapses all callers to a single shared Power Automate identity. It is safe for a single operator (or a dedicated service identity) but must not be exposed as a shared multi-user endpoint today. The Docker README/compose should carry an explicit "single-operator only" warning until the v2 per-user OAuth path lands.

Why (verified against the code)

Read the thread · 2026-06-03 · open · 0 comments

Consider a dedicated public-client app (vs reusing Civala-Microsoft365-MCP)

v0.1.1 reuses the shared MS365 Graph app, which forced specific scopes (not .default) and couples the two servers. A dedicated public-client app with only the Microsoft Flow Service delegated permission would be cleaner and could use .default. See docs/api-notes.md auth findings.

Read the thread · 2026-06-03 · open · 0 comments

Bump publish workflow off deprecated Node 20 actions

actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4, softprops/action-gh-release@v1 run on Node 20 (deprecated; forced to Node 24 by GitHub on 2026-06-16). Update action versions or set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24.

Read the thread · 2026-06-03 · open · 0 comments

Live-verify untested write tools

Exercised live: enable/disable, create/update/delete. NOT yet verified against a real tenant: cancel_flow_run, resubmit_flow_run, add_flow_owner, remove_flow_owner. Also confirm the add_flow_owner PUT permissions body shape (api-notes #8 — currently a guess: { properties: { principal: { id, type:'User' }, roleName } }).

Read the thread · 2026-06-03 · open · 0 comments

Committed .mcp.json defaults AZURE_TENANT_ID=common (Flow footgun)

The committed .mcp.json sets AZURE_TENANT_ID to 'common', which fails for the Flow audience (AADSTS50059). Should use ${AZURE_TENANT_ID} (no hardcoded common) + the verified FLOW_SCOPES default. (Jordan's local copy already overrides with ${MS365_*}.)

Read the thread · 2026-06-03 · open · 0 comments

Verify clientCredentials (app-only) mode against a real tenant

Built but never run live (api-notes #4). Confirm whether app-only can mint a service.flow.microsoft.com token at all and what Flow reach it has (likely no personal 'My Flows'). Document the limitation precisely.

Read the thread · 2026-06-03 · open · 0 comments

Add run_flow tool (on-demand trigger)

Trigger a manual/button flow on demand from the server (today only the scripts/diag-*.mjs do this). Flow: POST .../flows/{flow}/triggers/{trigger}/listCallbackUrl → POST the returned URL. Write-gated. This is the last capability scripts have that the MCP server doesn't.

Read the thread · 2026-06-03 · open · 0 comments

Most recent

The remaining reports are on the project's issue tracker.