Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Microsoft Work IQ Remote MCPShortlist candidate | Apify MCP ServerMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Microsoft · Publisher source ↗ | Community implementation com.apify · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Jun 16, 2026 | Repo: Sep 23, 2026 Package: Sep 21, 2026 |
| Popularity evidence | ||
| GitHub stars | Not documented | 8,235 GitHub stars · checked 2026-09-24T04:14:39.546000Z |
| Package downloads / 30 days | No reliable download data | 103,470 package downloads / 30 days · checked 2026-09-24T04:23:13.539000Z |
| Shared repository stars | 1,012 Shared repository stars (not MCP-specific) · checked 2026-09-25T18:35:00Z | Not documented |
| Shared-package downloads / 30 days | 47,986 shared-package downloads / 30 days (not MCP-specific) · checked 2026-08-14T18:46:26.000Z | Not documented |
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Microsoft identity + tenant consent/admin consent | Hosted mode supports OAuth or Authorization Bearer APIFY_TOKEN; local stdio uses APIFY_TOKEN. Discovery tools can be unauthenticated, and agentic payment tokens are additional alternatives. |
| Cost | Microsoft 365/Work IQ licensing applies | Actor and platform usage is chargeable according to Actor pricing; even free Actors incur platform usage. x402, Skyfire, and AGI payment paths are documented; no fixed MCP fee is stated. |
| Permissions | Microsoft 365 permission trimming/policy enforcement | Dynamically exposes Apify Actors, including web, social, maps, and e-commerce scrapers, plus run, dataset, key-value-store, and documentation tools. call-actor executes external Actors. |
| Data handling | emails, meetings, docs, Teams, people and other tenant data | Requests and Actor inputs are sent to Apify; run results can be stored in Apify datasets and key-value stores. Telemetry is enabled by default and stdio uses Sentry; detailed retention is not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Permission trimming/policy enforcement + Microsoft security policy. | Actor execution can scrape external sites, process personal or regulated data, incur spend, and return untrusted content. Restrict tools, use scoped tokens, review Actor pricing and terms, and control telemetry and storage. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-08-11 |
| Candidate evidence | 2026-09-25T18:35:00Z | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →