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.
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.
Start with the servers below, then review permissions, credentials, and client-specific setup before connecting production resources.
Browser automation and web scraping capabilities.
npx -y @modelcontextprotocol/server-puppeteerCloud browser automation and session management.
npx -y @browserbasehq/mcp-server-browserbaseEnd-to-end testing and browser automation.
npx -y @playwright/mcp-serverUse this category when the agent has a clear task that needs structured access, not as a default permission bundle for every chat.
Install one server, confirm the client can discover tools, run a harmless test, and document any tokens or paths as placeholders only.
Prefer read-only access first, avoid broad production credentials, and require review before write-capable or external-facing actions.
Before production access
Turn your selected browser servers into a reviewable deployment decision with permission scoring, prompt-injection checks, and rollout gates.