AI-powered MCP server that provides natural language control for browser automation. Built on Playwright with an intelligent sub-agent that handles tool orchestration, keeping browser automation details out of Claude's context window. Features OAuth authentication for Claude subscribers and seamless web task automation.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"browser-ai": {
"env": {
"PLAYWRIGHT_MCP_PATH": "@playwright/mcp@latest"
},
"args": [
"@qckfx/browser-ai"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An AI-powered MCP (Model Context Protocol) server that provides a natural language interface to browser automation. This server acts as an intelligent wrapper around the official Playwright MCP server, allowing you to control browsers using plain English commands through Claude.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @qckfx/browser-ai against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser / ai-ml
Persistent memory using a knowledge graph
Multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval — skill-guided workflows, no API keys.
MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for Browser Ai and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An AI-powered MCP (Model Context Protocol) server that provides a natural language interface to browser automation. This server acts as an intelligent wrapper around the official Playwright MCP server, allowing you to control browsers using plain English commands through Claude.
To install Browser AI for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @qckfx/browser-ai --client claude
npm install -g @qckfx/browser-ai
Or use directly with npx:
npx @qckfx/browser-ai
The Browser AI MCP server requires Anthropic API access. You have two authentication options:
If you have a Claude subscription, authenticate with your Claude account to use your subscription credits:
npx @qckfx/browser-ai --auth
This will open a browser window for OAuth authentication. After authorizing, the token will be saved securely and your API usage will be charged to your Claude subscription rather than requiring separate API credits.
Alternatively, you can use an Anthropic API key by setting the environment variable:
export ANTHROPIC_API_KEY="your-api-key-here"
After authentication, add the server to Claude Code:
claude mcp add browser-ai -- npx --yes @qckfx/browser-ai@latest
If using API key authentication, you can pass it as an environment variable:
claude mcp add browser-ai --env ANTHROPIC_API_KEY="your-api-key-here" -- npx --yes @qckfx/browser-ai@latest
If using Claude Desktop instead, add the following to your Claude Desktop configuration file (claude_desktop_config.json):
{
"mcpServers": {
"browser-ai": {
"command": "npx",
"args": ["@qckfx/browser-ai"],
"env": {
"PLAYWRIGHT_MCP_PATH": "@playwright/mcp@latest"
}
}
}
}
Once configured, you can use natural language commands in Claude to control browser automation:
browser-ai/
├── src/
│ ├── auth/ # OAuth authentication
│ ├── mcp/ # MCP server and client
│ ├── ai/ # AI agent and tool mapping
│ ├── provider/ # Custom AI SDK provider
│ └── index.ts # CLI entry point
git clone <repository>
cd browser-ai
npm install
npm run build
Run the integration test:
npm test
Enable debug logging