Microsoft Copilot Studio MCP vs Kestra

Microsoft Copilot Studio MCP

Entra sign-in with per-resource scopes, tokens kept only in memory, and a plan-then-confirm step before connector writes. The package is a day old, the linked MIT repository holds no source, no changelog or support channel exists, the five cloud tools' schemas are visible only after sign-in, and workflow tests run live workflows billed in Copilot Credits.

Kestra

Kestra's open-source edition has a 216-operation OpenAPI spec, Markdown docs for agents and weekly patch releases on two long-term support lines. Its only credential is one basic-auth username and password with full access, and five critical advisories were published between March and September 2026, all fixed.

Microsoft Copilot Studio MCP

1. Call copilot_studio_status first and reuse a ready session. Don't reconnect or reselect an environment to start a new task
2. Read an action's contract with discover_resources and action=describe_actions before building unfamiliar parameters
3. Ask the person before testing a workflow. Tests run published, enabled workflows and can have real effects
4. Never retry an uncertain write. Inspect the agent, workflow or connection first, as the error text says
5. Expect a browser sign-in after every restart. Tell the person a window is opening and never ask for credentials in chat

Kestra

1. Run 2.0.5 or 1.3.42 or later. Earlier builds carry unauthenticated remote code execution advisories fixed in 1.3.38 and 2.0.3
2. Set kestra.server.basic-auth in the config file before first start. Without it the setup page is open to anyone who reaches the port
3. Put the tenant in the path. Open-source instances use main, as in /api/v1/main/executions/{namespace}/{id}
4. Send flow inputs as multipart form fields, and add wait=true to get the finished execution in the same call
5. Keep port 8081 off any shared network. The management endpoints there skip the API's basic auth