qwen-browser-use-mcp-server

qwen-browser-use-mcp-server is an MCP (Model Context Protocol) server that exposes Qwen/Browse-automation browser-use capabilities to MCP clients (agents). It is intended to let an AI agent interact with a browser environment through MCP tools, presumably using Qwen as the underlying model for reasoning and browse assistance.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ DevTools mcp browser-automation ai-agent qwen tooling
⚙ Agent Friendliness
36
/ 100
Can an agent use this?
🔒 Security
42
/ 100
Is it safe for agents?
⚡ Reliability
21
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
40
Rate Limits
10

🔒 Security

TLS Enforcement
70
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
50

Security cannot be fully assessed from the provided input. As an MCP browser automation component, the primary risks typically include: inadvertent access to local resources via the execution environment, uncontrolled network access, credential leakage through logs/tool outputs, and dependency vulnerabilities. Verify sandboxing, network egress controls, least-privilege access, and robust secret handling before use.

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
20
Error Recovery
35
AF Security Reliability

Best When

You are building an MCP-enabled agent system that needs browser automation and are comfortable validating the MCP tool contracts and runtime security/sandboxing.

Avoid When

You cannot review or control the server’s browser execution environment (e.g., headless browser, filesystem/network access) or you need documented enterprise-grade security/compliance.

Use Cases

  • Letting an agent perform web browsing and information retrieval via MCP tools
  • Automating multi-step web tasks (navigation, reading, extracting) through an agent tool interface
  • Integrating browser automation into an MCP-based agent workflow

Not For

  • High-assurance production use without reviewing tool permissions, sandboxing, and dependency security
  • Use cases requiring strict data residency/compliance guarantees without explicit provider documentation
  • Real-time interactive browsing at scale where rate limits and concurrency controls are critical

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: MCP transport authentication (unspecified)
OAuth: No Scopes: No

No package-provided authentication details were included in the provided input, so auth strength/scope granularity cannot be confirmed.

Pricing

Free tier: No
Requires CC: No

No pricing/hosting model information was provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Browser tool actions can be non-deterministic due to dynamic web content and timing
  • Agents may need explicit limits/guards to prevent unintended repeated navigation or form submissions
  • Without clear guidance, agents can struggle to recover from navigation timeouts or element-not-found errors

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for qwen-browser-use-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered