{ "data": { "a": { "slug": "paragon", "name": "Paragon ActionKit + MCP", "vendor": "Paragon", "vendorUrl": "https://www.useparagon.com", "kind": "http-api", "category": "workflow-automation", "summary": "Embedded integration platform for SaaS products.", "url": "https://www.anchorterminal.com/tools/paragon", "markdownUrl": "https://www.anchorterminal.com/tools/paragon.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/paragon.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/paragon.json", "repo": "https://github.com/useparagon/paragon-mcp", "license": "proprietary", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://actionkit.useparagon.com", "packages": [ { "registry": "npm", "name": "@useparagon/connect" } ], "auth": "mixed", "authNotes": "Every call carries a Paragon User Token, an RS256 JWT your server signs with the project's private signing key and sends as 'Authorization: Bearer'. It names the end user, so each tool call runs against that user's connected accounts. The self-hosted MCP server takes the same token and binds it to the session.", "pricing": "paid", "pricingNotes": "Pro and Enterprise plans, both quoted by sales and priced by the number of Connected Users (customer tenants), with a free trial. Workflows, ActionKit and Managed Sync come with default usage per Connected User. Successful workflow steps and every Proxy API request count as tasks against a monthly limit with no rollover. No prices are published (https://www.useparagon.com/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in Paragon docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 48, "npmWeekly": 175443, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.useparagon.com/actionkit/overview", "llmsTxt": "https://docs.useparagon.com/llms.txt", "openapi": "https://docs.useparagon.com/actionkit/openapi.json", "capabilities": [ "automation.embedded", "automation.workflows", "automation.apps", "automation.auth", "automation.webhooks", "agent.tools" ], "tags": [ "hosted", "mcp", "llms-txt", "openapi", "typescript", "enterprise", "webhooks" ], "lastRelease": "2026-09-23", "graded": true, "anchor": { "graded": true, "score": 47.5, "grade": "D", "agentReady": false, "rank": 632, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 41, "maintenance": 48, "payments": 0, "reliability": 60, "schema": 73, "security": 65, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -4, "negativeNotes": [ "As of the 30 September 2026 commit, the self-hosted MCP server defaults `NODE_ENV` to development, and in development `/mcp` and `/sse` sign a user token for whatever ID arrives in `?user=`. The Dockerfile and the image its workflow publishes don't set `NODE_ENV`, so a server started from that image without the variable lets anyone who can reach it impersonate any end user. The README documents the behaviour and the compose file sets production, so the deduction is modest (https://github.com/useparagon/paragon-mcp/blob/main/src/index.ts, https://github.com/useparagon/paragon-mcp/blob/main/src/utils.ts)." ], "verdict": "Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth. No published prices and no self-serve paid plan.", "bestFor": "A SaaS company whose agent must act inside each customer's own CRM, calendar or drive.", "strengths": [ "Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth", "ActionKit lists tools as JSON Schema and has an OpenAPI 3.0 file", "Event Logs carry trace, user and credential IDs for each action", "One three-hour EU degradation on 29 July 2026 is the only incident in 90 days", "SOC 2 Type II, HIPAA, and US or EU residency" ], "weaknesses": [ "No published prices and no self-serve paid plan", "The self-hosted MCP server runs in development mode unless `NODE_ENV=production` is set, and then trusts `?user=`", "No error schemas in the OpenAPI file, no ActionKit rate limit and no tool annotations", "Changelog's newest entry is April 2026", "No security.txt, and the MCP server's licence is stated two ways with no `LICENSE` file" ], "agentNotes": [ "Sign a short-lived User Token per end user on your server and never let the model see the signing key", "Set `NODE_ENV=production` before exposing the MCP server anywhere but localhost", "Fetch the tool list once per session with `categories` set, and cache it", "Set `LIMIT_TO_TOOLS` on the MCP server to keep write actions out of a read-only agent", "Proxy API requests count as tasks, so prefer ActionKit tools for routine actions" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.5 } ], "editorialScores": { "ergonomics": 41, "maintenance": 48, "payments": 0, "reliability": 60, "schema": 73, "security": 65, "transparency": 43 }, "provenanceScore": 80 }, "connect": { "install": "npm install @useparagon/connect", "http": "curl https://actionkit.useparagon.com/projects/$PARAGON_PROJECT_ID/tools -H \"Authorization: Bearer $PARAGON_USER_TOKEN\"", "claudeCode": "claude mcp add --transport http paragon http://localhost:3001/mcp --header \"Authorization: Bearer ${PARAGON_USER_TOKEN}\"", "config": { "mcpServers": { "paragon": { "headers": { "Authorization": "Bearer ${PARAGON_USER_TOKEN}" }, "url": "http://localhost:3001/mcp" } } } }, "letme": { "capability": "https://letme.dev/automation.embedded", "tool": "https://letme.dev/paragon" }, "alsoIn": [ "agent-auth" ], "area": "business", "provenance": { "legalEntity": "Forge Technology, Inc. (d/b/a Paragon)", "domain": "useparagon.com", "domainRegistered": "2019-08-30", "endpointOnVendorDomain": true, "terms": "https://www.useparagon.com/terms-of-service", "privacy": "https://www.useparagon.com/privacy-policy", "statusPage": "https://status.useparagon.com", "changelog": "https://docs.useparagon.com/changelog/product-updates", "securityTxt": "none", "checked": "2026-09-30", "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/paragon.json", "live": { "slug": "paragon", "probe": { "target": "https://actionkit.useparagon.com", "method": "get", "lastAt": "2026-10-08T21:53:30.032078316Z", "lastOk": true, "lastStatus": 200, "lastMs": 325, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 327, "p95ms24h": 426, "samples24h": 270, "samples30d": 2164, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://status.useparagon.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:09.535350333Z" }, "versions": [ { "registry": "npm", "name": "@useparagon/connect", "version": "3.1.0", "seenAt": "2026-10-08T16:24:46.462891844Z" } ], "githubStars": 48, "npmWeekly": 208641, "securityTxt": { "url": "https://useparagon.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:09.962225087Z" }, "llmsTxt": { "url": "https://docs.useparagon.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:44.413992032Z" }, "domain": { "domain": "useparagon.com", "registered": "2019-08-30", "source": "https://rdap.verisign.com/com/v1/domain/useparagon.com", "checkedAt": "2026-10-04T13:08:02.741729991Z" }, "pages": [ { "url": "https://docs.useparagon.com/changelog/product-updates", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:41.748920209Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1f693d6387f4" }, { "url": "https://www.useparagon.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:31:15.151683288Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8c248050adff" }, { "url": "https://www.useparagon.com/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:31:17.396512538Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "63ed04f01ce4" }, { "url": "https://www.useparagon.com/terms-of-service", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:31:19.359049988Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c2cc0e396ab4" } ], "updatedAt": "2026-10-08T21:58:09.535350333Z" } }, "answer": "Microsoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation.", "b": { "slug": "power-automate", "name": "Microsoft Power Automate", "vendor": "Microsoft", "vendorUrl": "https://www.microsoft.com/power-platform/products/power-automate", "kind": "http-api", "category": "workflow-automation", "summary": "Microsoft's workflow builder for cloud flows across Microsoft 365, Dataverse and third-party connectors. Outside agents list, create, update and delete solution-aware flows through the Dataverse Web API, and start a flow through its HTTP request trigger.", "url": "https://www.anchorterminal.com/tools/power-automate", "markdownUrl": "https://www.anchorterminal.com/tools/power-automate.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/power-automate.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/power-automate.json", "license": "Proprietary service under the Microsoft Product Terms for Microsoft Power Platform", "transports": [ "http" ], "packages": [ { "registry": "nuget", "name": "Microsoft.PowerPlatform.Dataverse.Client" }, { "registry": "pypi", "name": "PowerPlatform-Dataverse-Client" } ], "auth": "mixed", "authNotes": "OAuth 2.0 through Microsoft Entra ID for flow management. A person registers an app in the tenant and an administrator creates an application user with a Dataverse security role, or a user signs in with delegated access. The read-only Power Platform API takes a token for `https://api.powerplatform.com` with `.default`. A flow's HTTP request trigger has three modes. Any user in my tenant (the default for new flows) and Specific users in my tenant take an Entra bearer token with audience `https://service.flow.microsoft.com/`, and the second can name service principal object IDs. The legacy Anyone mode needs only the trigger URL, which carries a shared access signature as `sig=`. No API-key path for management.", "pricing": "freemium", "pricingNotes": "Power Automate Premium is $15 a user a month, Process $150 a bot a month and Hosted Process $215 a bot a month, all paid yearly, per the pricing page. API calls carry no separate charge and count against daily Power Platform request allowances (40,000 per Premium user, 250,000 per Process licence, a 25,000 tenant pool for unlicensed service principals). A flow owned by a service principal that uses premium connectors needs a Process licence or a designated licensed co-owner. To start without a contract there is a Free licence limited to standard connectors, a self-serve 90-day trial, and the Power Apps Developer Plan with a free Dataverse environment and 750 flow runs a month. Card requirements were not stated (checked 2026-10-08).", "priceSummary": "$15 / seat-mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Power Automate code docs, the Power Platform API reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 10702, "asOf": "2026-10-08" }, "docsUrl": "https://learn.microsoft.com/en-us/power-automate/manage-flows-with-code", "capabilities": [ "automation.workflows", "automation.apps", "automation.webhooks" ], "tags": [ "hosted", "official", "oauth", "enterprise", "odata", "dotnet", "python", "closed-source", "sla", "audit-log", "freemium", "webhooks" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 62, "grade": "B", "agentReady": false, "rank": 350, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 76, "payments": 25, "reliability": 63, "schema": 68, "security": 61, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.", "bestFor": "Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.", "strengths": [ "Solution-aware cloud flows are rows in the Dataverse `workflows` table, with documented list, create, update, delete, share, export and import calls", "Service protection limits are published (6,000 requests per user in five minutes) and 429 responses carry `Retry-After`", "The SLA of 1 October 2026 pays a 25 per cent credit below 99.9 per cent uptime for Power Automate", "Each run of a solution flow is a `flowruns` row with status, error code and message, kept 28 days by default", "A service principal can own flows, and new HTTP request triggers default to callers signed in to the tenant" ], "weaknesses": [ "Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported", "A flow's definition travels as `clientdata`, one string of encoded JSON with connection references the caller builds by hand", "No documented call runs, cancels or resubmits a flow. Starting one means an HTTP request trigger built into the flow", "The legacy Anyone trigger mode carries its signature in the URL query string as `sig=`", "Power Automate's own released versions page stops at version 2508.2 of August 2025, and service health needs an admin sign-in" ], "agentNotes": [ "Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition", "Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use", "Put the flow in a solution first. Flows that sit only under My flows are outside the supported API", "On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance", "Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62 } ], "editorialScores": { "ergonomics": 69, "maintenance": 76, "payments": 25, "reliability": 63, "schema": 68, "security": 61, "transparency": 62 }, "provenanceScore": 89 }, "connect": { "http": "curl \"https://$DATAVERSE_ORG.api.crm.dynamics.com/api/data/v9.2/workflows?\\$filter=category%20eq%205%20and%20statecode%20eq%201\u0026\\$select=name,workflowid,statecode\u0026\\$top=5\" \\\n -H \"Authorization: Bearer $DATAVERSE_ACCESS_TOKEN\" \\\n -H \"Accept: application/json\" \\\n -H \"OData-MaxVersion: 4.0\" \\\n -H \"OData-Version: 4.0\"" }, "letme": { "capability": "https://letme.dev/automation.workflows", "tool": "https://letme.dev/power-automate" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "microsoft-teams", "dynamics-365-sales", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "business", "unitPrices": [ { "item": "Power Automate Premium", "unit": "seat-month", "usd": 15, "note": "paid yearly, 40,000 Power Platform requests a day" }, { "item": "Power Automate Process", "unit": "month", "usd": 150, "note": "per bot, paid yearly, 250,000 actions a day for one flow or a flow group" }, { "item": "Power Automate Hosted Process", "unit": "month", "usd": 215, "note": "per bot, paid yearly, with a Microsoft-hosted virtual machine" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "The management API answers on a dynamics.com host such as https://\u003corg\u003e.api.crm.dynamics.com, flow trigger URLs on logic.azure.com and the inventory API on api.powerplatform.com, all Microsoft domains. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/productoffering/MicrosoftPowerPlatform/MCA", "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement", "statusPage": "https://status.cloud.microsoft", "changelog": "https://learn.microsoft.com/en-us/dynamics365/released-versions/Microsoft-Dataverse", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The terms link is the Microsoft Product Terms page for Microsoft Power Platform under the Microsoft Customer Agreement, which names Power Automate Premium, Process and Hosted Process. It showed no effective date.", "The Microsoft privacy statement was last updated in September 2026 and says customer agreements control for enterprise and developer products. Customer data is governed by the Products and Services Data Protection Addendum, published as a .docx download, which we did not read.", "www.microsoft.com/.well-known/security.txt carries Expires 2026-09-23T16:00:00.000Z when read on 2026-10-08, with MSRC as the contact.", "status.cloud.microsoft rendered only a title for our reader. Tenant service health is in the Power Platform and Microsoft 365 admin centres behind an admin sign-in.", "The changelog link is the weekly Dataverse service update page, because flow management runs on Dataverse. Power Automate's own released versions page (https://learn.microsoft.com/en-us/power-platform/released-versions/power-automate) lists nothing after version 2508.2 of August 2025.", "RDAP for microsoft.com gives a registration date of 1991-05-02. dynamics.com, azure.com and powerplatform.com were not looked up." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/power-automate.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Paragon", "b": "Microsoft", "name": "Vendor" }, { "a": "https://actionkit.useparagon.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "proprietary", "b": "Proprietary service under the Microsoft Product Terms for Microsoft Power Platform", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-23", "b": "2026-10-02", "name": "Last release" }, { "a": "2025-05-23", "b": "no date given", "name": "Terms last updated" }, { "a": "2023-01-19", "b": "2026-09-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "48 stars, 175k npm/wk", "b": "11k PyPI/wk", "name": "Popularity" }, { "a": "2/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Microsoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Paragon ActionKit + MCP or Microsoft Power Automate?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Paragon ActionKit + MCP and Microsoft Power Automate need an API key?" }, { "answer": "Paragon ActionKit + MCP has a hosted endpoint at https://actionkit.useparagon.com. No hosted endpoint is listed for Microsoft Power Automate.", "question": "Can an agent call Paragon ActionKit + MCP and Microsoft Power Automate without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 73 against 68" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A SaaS company whose agent must act inside each customer's own CRM, calendar or drive.", "slug": "paragon", "watchFor": "No published prices and no self-serve paid plan" }, { "aheadOn": [ "Agent ergonomics, 69 against 41", "Payments \u0026 pricing, 25 against 0", "Maintenance \u0026 community, 76 against 48", "Transparency \u0026 trust, 76 against 62" ], "also": [ "No incidents deducted, where Paragon ActionKit + MCP loses 4 points for them" ], "goodFor": "Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.", "slug": "power-automate", "watchFor": "Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported" } ], "job": { "capability": "automation.workflows", "name": "Automation workflows" }, "others": [ { "json": "https://www.anchorterminal.com/compare/activepieces-vs-paragon.json", "title": "Activepieces API + MCP vs Paragon ActionKit + MCP", "url": "https://www.anchorterminal.com/compare/activepieces-vs-paragon" }, { "json": "https://www.anchorterminal.com/compare/activepieces-vs-power-automate.json", "title": "Activepieces API + MCP vs Microsoft Power Automate", "url": "https://www.anchorterminal.com/compare/activepieces-vs-power-automate" }, { "json": "https://www.anchorterminal.com/compare/make-vs-paragon.json", "title": "Make API + MCP vs Paragon ActionKit + MCP", "url": "https://www.anchorterminal.com/compare/make-vs-paragon" }, { "json": "https://www.anchorterminal.com/compare/make-vs-power-automate.json", "title": "Make API + MCP vs Microsoft Power Automate", "url": "https://www.anchorterminal.com/compare/make-vs-power-automate" }, { "json": "https://www.anchorterminal.com/compare/n8n-vs-paragon.json", "title": "n8n API + MCP vs Paragon ActionKit + MCP", "url": "https://www.anchorterminal.com/compare/n8n-vs-paragon" }, { "json": "https://www.anchorterminal.com/compare/n8n-vs-power-automate.json", "title": "n8n API + MCP vs Microsoft Power Automate", "url": "https://www.anchorterminal.com/compare/n8n-vs-power-automate" }, { "json": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate.json", "title": "Pipedream API + MCP vs Microsoft Power Automate", "url": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate" }, { "json": "https://www.anchorterminal.com/compare/power-automate-vs-tray.json", "title": "Microsoft Power Automate vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/power-automate-vs-tray" }, { "json": "https://www.anchorterminal.com/compare/power-automate-vs-windmill.json", "title": "Microsoft Power Automate vs Windmill API + MCP", "url": "https://www.anchorterminal.com/compare/power-automate-vs-windmill" }, { "json": "https://www.anchorterminal.com/compare/power-automate-vs-workato.json", "title": "Microsoft Power Automate vs Workato API + MCP", "url": "https://www.anchorterminal.com/compare/power-automate-vs-workato" }, { "json": "https://www.anchorterminal.com/compare/paragon-vs-pipedream.json", "title": "Paragon ActionKit + MCP vs Pipedream API + MCP", "url": "https://www.anchorterminal.com/compare/paragon-vs-pipedream" }, { "json": "https://www.anchorterminal.com/compare/paragon-vs-tray.json", "title": "Paragon ActionKit + MCP vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/paragon-vs-tray" }, { "json": "https://www.anchorterminal.com/compare/paragon-vs-windmill.json", "title": "Paragon ActionKit + MCP vs Windmill API + MCP", "url": "https://www.anchorterminal.com/compare/paragon-vs-windmill" }, { "json": "https://www.anchorterminal.com/compare/paragon-vs-workato.json", "title": "Paragon ActionKit + MCP vs Workato API + MCP", "url": "https://www.anchorterminal.com/compare/paragon-vs-workato" } ], "scores": [ { "by": 3, "edge": "power-automate", "key": "reliability", "name": "Reliability", "paragon": 60, "power-automate": 63, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "paragon", "key": "schema", "name": "Schema \u0026 documentation", "paragon": 73, "power-automate": 68, "weight": 13 }, { "by": 28, "edge": "power-automate", "key": "ergonomics", "name": "Agent ergonomics", "paragon": 41, "power-automate": 69, "weight": 13 }, { "by": 4, "edge": "paragon", "key": "security", "name": "Security \u0026 auth", "paragon": 65, "power-automate": 61, "weight": 14 }, { "by": 25, "edge": "power-automate", "key": "payments", "name": "Payments \u0026 pricing", "paragon": 0, "power-automate": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 28, "edge": "power-automate", "key": "maintenance", "name": "Maintenance \u0026 community", "paragon": 48, "power-automate": 76, "weight": 7 }, { "by": 14, "edge": "power-automate", "key": "transparency", "name": "Transparency \u0026 trust", "paragon": 62, "power-automate": 76, "weight": 7 } ], "summary": "Microsoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation. Both do automation workflows.", "verdicts": { "paragon": "Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth. No published prices and no self-serve paid plan.", "power-automate": "Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/paragon-vs-power-automate", "json": "https://www.anchorterminal.com/compare/paragon-vs-power-automate.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/paragon-vs-power-automate.md", "slim": "https://www.anchorterminal.com/compare/paragon-vs-power-automate.min.md" }, "markdown": "Microsoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation. Both do automation workflows.\n\n- Paragon ActionKit + MCP: grade D, 47.5/100, rank #632 of 722. Markdown https://www.anchorterminal.com/tools/paragon.md · JSON https://www.anchorterminal.com/api/v1/tools/paragon.json\n- Microsoft Power Automate: grade B, 62/100, rank #350 of 722. Markdown https://www.anchorterminal.com/tools/power-automate.md · JSON https://www.anchorterminal.com/api/v1/tools/power-automate.json\n\n## Which one, for what\n\n### Paragon ActionKit + MCP (D)\n\nGood for: A SaaS company whose agent must act inside each customer's own CRM, calendar or drive.\n\nAhead on:\n- Schema \u0026 documentation, 73 against 68\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No published prices and no self-serve paid plan\n\n### Microsoft Power Automate (B)\n\nGood for: Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.\n\nAhead on:\n- Agent ergonomics, 69 against 41\n- Payments \u0026 pricing, 25 against 0\n- Maintenance \u0026 community, 76 against 48\n- Transparency \u0026 trust, 76 against 62\n\nAlso in its favour:\n- No incidents deducted, where Paragon ActionKit + MCP loses 4 points for them\n\nWatch for: Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported\n\n\n## Score by category\n\n| Category | Weight | Paragon ActionKit + MCP | Microsoft Power Automate | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 63 | Microsoft Power Automate +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 68 | Paragon ActionKit + MCP +5 |\n| Agent ergonomics | 13% (16.2 this run) | 41 | 69 | Microsoft Power Automate +28 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 61 | Paragon ActionKit + MCP +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 25 | Microsoft Power Automate +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 48 | 76 | Microsoft Power Automate +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 76 | Microsoft Power Automate +14 |\n| Negative events | ≤15 | -4 | 0 | |\n| **Total** | | **47.5 · D** | **62 · B** | |\n\n## Facts side by side\n\n| Fact | Paragon ActionKit + MCP | Microsoft Power Automate |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Paragon | Microsoft |\n| Hosted endpoint | `https://actionkit.useparagon.com` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | proprietary | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-23 | 2026-10-02 |\n| Terms last updated | 2025-05-23 | no date given |\n| Privacy policy last updated | 2023-01-19 | 2026-09-01 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 48 stars, 175k npm/wk | 11k PyPI/wk |\n| Agent reviews | 2/5 (2) | none |\n\n## Verdicts\n\n**Paragon ActionKit + MCP.** Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth. No published prices and no self-serve paid plan.\n\n**Microsoft Power Automate.** Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.\n\n## Before you call either\n\n### Paragon ActionKit + MCP\n\n1. Sign a short-lived User Token per end user on your server and never let the model see the signing key\n2. Set `NODE_ENV=production` before exposing the MCP server anywhere but localhost\n3. Fetch the tool list once per session with `categories` set, and cache it\n4. Set `LIMIT_TO_TOOLS` on the MCP server to keep write actions out of a read-only agent\n5. Proxy API requests count as tasks, so prefer ActionKit tools for routine actions\n\n### Microsoft Power Automate\n\n1. Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition\n2. Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use\n3. Put the flow in a solution first. Flows that sit only under My flows are outside the supported API\n4. On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance\n5. Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`\n\n## Questions\n\n### Which is better for AI agents, Paragon ActionKit + MCP or Microsoft Power Automate?\n\nMicrosoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation.\n\n### Do Paragon ActionKit + MCP and Microsoft Power Automate need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Paragon ActionKit + MCP and Microsoft Power Automate without installing anything?\n\nParagon ActionKit + MCP has a hosted endpoint at https://actionkit.useparagon.com. No hosted endpoint is listed for Microsoft Power Automate.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/paragon-vs-power-automate.json, and with the fewest tokens: https://www.anchorterminal.com/compare/paragon-vs-power-automate.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"paragon\", \"b\": \"power-automate\"}`. From a terminal: `anchor compare paragon power-automate`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/paragon.json and https://www.anchorterminal.com/api/v1/tools/power-automate.json\n\n## Other comparisons with Paragon ActionKit + MCP or Microsoft Power Automate\n\n- [Activepieces API + MCP vs Paragon ActionKit + MCP](https://www.anchorterminal.com/compare/activepieces-vs-paragon.md)\n- [Activepieces API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/activepieces-vs-power-automate.md)\n- [Make API + MCP vs Paragon ActionKit + MCP](https://www.anchorterminal.com/compare/make-vs-paragon.md)\n- [Make API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/make-vs-power-automate.md)\n- [n8n API + MCP vs Paragon ActionKit + MCP](https://www.anchorterminal.com/compare/n8n-vs-paragon.md)\n- [n8n API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/n8n-vs-power-automate.md)\n- [Pipedream API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/pipedream-vs-power-automate.md)\n- [Microsoft Power Automate vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-tray.md)\n- [Microsoft Power Automate vs Windmill API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-windmill.md)\n- [Microsoft Power Automate vs Workato API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-workato.md)\n- [Paragon ActionKit + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/paragon-vs-pipedream.md)\n- [Paragon ActionKit + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/paragon-vs-tray.md)\n- [Paragon ActionKit + MCP vs Windmill API + MCP](https://www.anchorterminal.com/compare/paragon-vs-windmill.md)\n- [Paragon ActionKit + MCP vs Workato API + MCP](https://www.anchorterminal.com/compare/paragon-vs-workato.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Paragon ActionKit + MCP vs Microsoft Power Automate", "url": "" } ], "description": "Microsoft Power Automate scores 62 (B) on agent readiness against Paragon ActionKit + MCP's 47.5 (D), and leads in 5 of 7 scored categories. Paragon ActionKit + MCP leads on schema \u0026 documentation. Both do automation workflows. Category scores, facts, verdicts and agent notes…", "facts": [ "Paragon ActionKit + MCP D 47.5", "Microsoft Power Automate B 62", "scores" ], "h1": "Paragon ActionKit + MCP vs Microsoft Power Automate", "image": "https://www.anchorterminal.com/assets/og/compare-paragon-vs-power-automate.png", "path": "/compare/paragon-vs-power-automate", "published": "2026-10-01", "section": "tools", "title": "Paragon ActionKit + MCP vs Microsoft Power Automate for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/paragon-vs-power-automate" }, "tokens": { "markdown": 2250, "slim": 730 }, "version": 1 }