# Selenium MCP server

> Run controlled browser tasks and return verifiable results.

- Provider: Selenium
- Category: Browser Automation (https://mcpheaven.com/catalog/category/browser-automation)
- Status: Planned
- Slug: `selenium`
- Verified: 2026-11-10
- JSON: https://mcpheaven.com/api/v1/capabilities/selenium
- HTML: https://mcpheaven.com/catalog/selenium

## Why it is in the catalog

Browser automation framework with community MCP wrappers but no official MCP distribution.

## Questions

### Is there an official Selenium MCP server?

Browser automation framework with community MCP wrappers but no official MCP distribution. mcpheaven lists Selenium so agents can find it by task and reach it through one MCP endpoint.

### What can an AI agent do with Selenium?

Run controlled browser tasks and return verifiable results. Agents find it by describing the task, for example with the search_capabilities tool.

### How do I connect Selenium to Claude, Codex or Cursor?

Add mcpheaven once as an MCP server (https://mcpheaven.com/mcp) with an API key, then ask your agent for the task. It calls get_capability with the slug "selenium" for details.

### Is the Selenium integration available?

The Selenium integration is planned. Agents can already discover it through mcpheaven's search, and it will become callable once the integration ships.

## Connect

MCP endpoint: `https://mcpheaven.com/mcp` (Streamable HTTP, JSON-RPC). Without a key: public catalog, 120 calls per hour per address. With a key (`Authorization: Bearer mch_…`, free at https://mcpheaven.com/signup): plan quota and private capabilities.

```bash
claude mcp add --transport http mcpheaven https://mcpheaven.com/mcp --header "Authorization: Bearer mch_…"
```

```json
{ "mcpServers": { "mcpheaven": { "url": "https://mcpheaven.com/mcp", "headers": { "Authorization": "Bearer mch_…" } } } }
```

REST: `GET https://mcpheaven.com/api/v1/capabilities?q=<task>` · OpenAPI: https://mcpheaven.com/openapi.json · Server card: https://mcpheaven.com/.well-known/mcp.json