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 | Terraform MCPWatchlist candidate | Azure MCP ServerMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP HashiCorp · Publisher source ↗ | First-party MCP Microsoft · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 13, 2026 |
| Popularity evidence | ||
| GitHub stars | 1,503 GitHub stars · checked 2026-08-14T18:46:26.000Z | 3,514 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | No reliable download data | 477,796 30-day package downloads · checked 2026-08-14T18:46:26.000Z |
| Shared repository stars | Not documented | 3,566 Shared repository stars (not MCP-specific) · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| 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✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Follow only the publisher source; credential storage, scopes, and revocation remain under review. | The local server uses Azure's established authentication chain, commonly Azure CLI sign-in or other Microsoft identity credentials. No credential should be embedded in MCP JSON; use a dedicated least-privilege identity or subscription context. |
| Cost | Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion. | The MIT-licensed server has no separately documented MCP charge. Azure resources created or queried, network usage, logs, and the AI client remain subject to their normal plans and charges. |
| Permissions | Exact permissions and read/write boundaries have not completed MCP100 review. | Tools invoke Azure operations using the current Azure authentication context, and Azure RBAC determines effective access. Depending on enabled services and roles, the server can read, create, update, or delete cloud resources and retrieve logs or configuration. |
| Data handling | Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items. | Azure resource identifiers, configuration, logs, command inputs, and results may be returned to the MCP client. Microsoft documents optional usage telemetry that can be disabled with AZURE_MCP_COLLECT_TELEMETRY=false; normal Azure service requests remain visible to Azure. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Use a test account, least privilege, read-only controls where available, and explicit approval for mutations. | A broadly privileged Azure identity can make the agent an infrastructure administrator. Use a non-production subscription for evaluation, least-privilege RBAC, explicit subscription/resource-group targeting, telemetry choice, activity logs, budgets, and confirmation before every mutation. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →