Selenium doesn't need MCP

[p0deje]

User description

Description

Adds a blog post to clarify the Selenium project's stance on whether it should include an official MCP server.

Motivation and Context

It's been repeatedly asked in bug trackers and Slack channels.

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Documentation

---

Description

• Adds blog post explaining Selenium's stance on MCP server implementation

• Discusses context window limitations and token consumption issues

• Compares tool calling vs code execution approaches for AI agents

• Advocates for ecosystem-based solutions over native MCP integration

---

Diagram Walkthrough

flowchart LR
  A["Selenium Project"] -->|"Clarifies stance"| B["MCP Server Question"]
  B -->|"Identifies problems"| C["Context Window Limitations"]
  C -->|"Proposes alternative"| D["Ecosystem-based Solutions"]
  D -->|"Recommends"| E["Code Execution via Bindings"]

Loading

File Walkthrough

Relevant files

Documentation

why-selenium-doesnt-need-mcp.md Blog post on Selenium MCP server rationale                              website_and_docs/content/blog/2025/why-selenium-doesnt-need-mcp.md New blog post addressing recurring community question about official MCP server Explains why native MCP integration is inefficient for LLM agents Details context window management challenges with naive tool exposure Compares tool calling vs code execution paradigms for agent automation Advocates for ecosystem projects to handle MCP implementation instead +77/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Clarify the contribution call to action Clarify the contribution call to action in the footnote by replacing the ambiguous "add it here" text with a direct link to edit the relevant ecosystem page on GitHub. website_and_docs/content/blog/2025/why-selenium-doesnt-need-mcp.md [77] -<sup>1</sup> _If you are familiar with an open source project based on the WebDriver ecosystem not listed there, please add it here and send us a pull request._ +<sup>1</sup> _If you are familiar with an open source project based on the WebDriver ecosystem not listed there, please [send us a pull request to add it](https://github.com/SeleniumHQ/seleniumhq.github.io/edit/master/website_and_docs/content/ecosystem.en.md)._ Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies an ambiguous call to action in the footnote and proposes a much clearer, actionable link for community contributions, which improves the user experience for potential contributors.	Low
Update

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	9c39df4
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/6945d6c34064e700087c79e2
😎 Deploy Preview	https://deploy-preview-2558--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[titusfortner]

This is excellent.

I gave suggestions for making the title/subtitle stronger, and then more feedback on the GitHub paragraph for consideration.

[rpallavisharma]

Informative blog post. Thanks for writing and explaining Alex @p0deje . places where it says ours we may say Selenium or
Project.

And I just have a question the article ends with saying once the problems with mcp are solved we might see what to do..

selenium project has ide , has grid these are beyond the WebDriver bidi low level implementations.
Similarly selenium manager came into being..

Is it better to say why there is nothing official from project yet and have that approach because of the challenges and technicalities the blog mentions? That's just a thought that I had.

Just a thought to keep it open ended maybe.. as project decides... how to proceed further ..

[p0deje]

@rpallavisharma Thank you for taking the time to read it and share your feedback. I'm planning to significantly rewrite this based on this and other folks comments,