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 | browserstackMCP100 Recommended | Terraform MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP ecosystem:browserstack · Publisher source ↗ | First-party MCP HashiCorp · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Sep 23, 2026 Package: Sep 21, 2026 | Repo: Aug 14, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 152 GitHub stars · checked 2026-09-24T04:14:26.334000Z | 1,534 GitHub stars · checked 2026-09-25T18:35:00Z |
| Package downloads / 30 days | 61,452 package downloads / 30 days · checked 2026-09-24T04:17:50.285000Z | No reliable download data |
| 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 | The official package uses BrowserStack credentials documented by the publisher. | HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN |
| Cost | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. | HCP/TFE/run costs may apply |
| Permissions | BrowserStack account, project, product entitlements, and access credentials govern available tests and results. | HCP Terraform/TFE RBAC |
| Data handling | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive browser automation information. | registry/HCP/TFE data may reach connected MCP client/LLM |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Test execution consumes plan capacity and may interact with externally hosted applications. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. | stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default |
| Evidence date | ||
| Editorial review | 2026-07-30 | 2026-07-24 |
| Candidate evidence | 2026-09-24T04:25:05.554391Z | 2026-09-25T18:35:00Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →