← MCP Server Directory

Browser MCP Servers

Browser MCP Servers

Browser MCP servers let agents inspect pages, automate flows, and collect web evidence, but they should be isolated from destructive tools and secrets.

Recommended browser servers

Start with the servers below, then review permissions, credentials, and client-specific setup before connecting production resources.

Review security checklist →
Browser

Browser automation and web scraping capabilities.

ClaudeCursorGeneric
npx -y @modelcontextprotocol/server-puppeteer

Cloud browser automation and session management.

ClaudeCursorGeneric
npx -y @browserbasehq/mcp-server-browserbase
Browser

End-to-end testing and browser automation.

ClaudeCursorGeneric
npx -y @playwright/mcp-server

Best first use case

Use this category when the agent has a clear task that needs structured access, not as a default permission bundle for every chat.

Setup checklist

Install one server, confirm the client can discover tools, run a harmless test, and document any tokens or paths as placeholders only.

Safety boundary

Prefer read-only access first, avoid broad production credentials, and require review before write-capable or external-facing actions.

Before production access

Audit permissions, secrets, and rollback controls

Turn your selected browser servers into a reviewable deployment decision with permission scoring, prompt-injection checks, and rollout gates.

Open the Audit Pack