Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
MCP server for Safari DevTools — browser debugging and automation for AI coding agents
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"safari-devtools": {
"command": "npx",
"args": [
"-y",
"safari-devtools-mcp"
]
}
}
}Run this in your terminal
claude mcp add safari-devtools -- npx -y safari-devtools-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"safari-devtools": {
"command": "npx",
"args": [
"-y",
"safari-devtools-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"safari-devtools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"safari-devtools-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account HayoDev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.8.1) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
safari-devtools-mcp lets your coding agent (such as Claude, Cursor, Copilot or Gemini) control and inspect a live Safari browser on macOS. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to Safari DevTools for debugging, automation, and testing.
Chrome developers get powerful AI debugging through chrome-devtools-mcp by Google. Safari developers should have something equivalent — this project brings that same experience to Safari, with matching tool names and parameter schemas so you can swap between browsers with minimal friction.
Note: This server exposes browser content (page data, console logs, network traffic) to MCP clients. Avoid browsing sensitive websites or entering credentials while a session is active.
This project uses WebDriver for capabilities that scripting alone cannot provide:
sudo safaridriver --enable
Standard MCP config:
{
"mcpServers": { "safari-devtools": { "command": "npx", "args": ["-y", "safari-devtools-mcp@latest"] } } }
Claude Code
claude mcp add safari-devtools -- npx -y safari-devtools-mcp@latest
Or add to your project's .mcp.json using the standard config above.
Claude Desktop
Add the standard config to ~/Library/Application Support/Claude/claude_desktop_config.json.
Cursor
Add the standard config to your Cursor MCP settings.
VS Code
Add the standard config to .vscode/mcp.json.
Copilot CLI
copilot mcp add safari-devtools -- npx -y safari-devtools-mcp@latest
Gemini CLI
gemini mcp add safari-devtools -- npx -y safari-devtools-mcp@latest
Or add the standard config to your ~/.gemini/settings.json.
Gemini Code Assist
Add the standard config to your .gemini/settings.json in the project root.
JetBrains AI Assistant & Junie
Add the standard config to your .junie/mcp.json in the project root.
Raycast
Open "Install MCP Server" in Raycast and fill in:
npx-y safari-devtools-mcp@latestOr copy the standard config JSON above before opening the command — Raycast will auto-fill the form.
Visual Studio
Add the standard config to your .vs/mcp.json in the solution root.
Warp
Add the standard config to your Warp MCP settings file at ~/.warp/mcp.json.
From source
git clone https://github.com/HayoDev/safari-devtools-mcp.git
cd safari-devtools-mcp npm install && npm run build
Then point your MCP client to the built entry point:
{
"mcpServers": { "safari-devtools": { "command": "node", "args": [ "/path/to/safari-devtools-mcp/build/src/bin/safari-devtools-mcp.js" ] } } }
Navigate to https://example.com, take a snapshot, and list any console errors.
Use --slim to reduce token usage with shorter tool descriptions. Useful when working with context-limited models or long conversations:
{
"mcpServers": { "safari-devtools": { "command": "npx", "args": ["-y", "safari-devtools-mcp@latest", "--slim"] } } }
The server exposes guided debugging workflows as MCP prompts. Clients that support prompts (e.g. Claude Desktop, Claude Code) can invoke them by name:
| Prompt | Description |
|---|---|
safari-devtools | Getting started — tool overview, recommended workflow, and Safari-specific notes |
a11y-debugging | Accessibility audit — a11y tree inspection, axe-core injection, WCAG checks |
safari-specific-debugging | Debug WebKit quirks — CSS prefixes, JS feature gaps, ITP/CORS issues |
performance-debugging | Performance analysis — Navigation Timing, Core Web Vitals, resource waterfall |
| Tool | Description |
|---|---|
list_console_messages | List console messages with filtering by level (log, warn, error) |
get_console_message | Get a detailed message including stack trace and arguments |
clear_console | Clear all captured console messages |
list_network_requests | Monitor network requests — Fetch, XHR, and resource loads |
get_network_request | Get full request/response details with headers and body |
clear_network | Clear all captured network requests |
evaluate_script | Execute JavaScript in the browser context and return results |
take_screenshot | Capture a PNG screenshot of the page or a specific element |
take_snapshot | Accessibility-tree snapshot of the DOM with stable UIDs for element targeting |
| Tool | Description |
|---|---|
get_page_content | Get the page title, URL, and visible text content |
get_html_source | Get the full HTML source of the page |
extract_links | Extract all links with their text, href, and rel attributes |
extract_meta | Extract meta tags (og:, twitter:, description, etc.) |
| Tool | Description |
|---|---|
list_pages | List all open Safari tabs across windows |
select_page | Switch to a specific tab |
new_page | Open a new tab and navigate to a URL |
close_page | Close a tab |
navigate_page | Navigate to a URL, go back, forward, or reload |
wait_for | Wait for specific text to appear on the page |
resize_page | Resize the browser window |
handle_dialog | Accept or dismiss browser dialogs (alert, confirm, prompt) |
| Tool | Description |
|---|---|
scroll | Scroll the page in any direction by a given amount |
scroll_to_element | Scroll an element into view by its UID |
| Tool | Description |
|---|---|
get_computed_style | Get computed CSS styles for any element by UID |
| Tool | Description |
|---|---|
get_cookies | Get browser cookies, optionally filtered by name or domain |
set_cookie | Set a cookie with name, value, and optional attributes |
delete_cookie | Delete a cookie by name, or delete all cookies |
get_storage | Read from localStorage or sessionStorage |
set_storage | Write a key-value pair to localStorage or sessionStorage |
delete_storage | Delete a key or clear all entries from localStorage/sessionStorage |
| Tool | Description |
|---|---|
click | Click an element by UID from a snapshot |
click_at | Click at specific x/y coordinates |
right_click | Right-click (context menu) on an element |
select_option | Select an option from a dropdown by value or label |
hover | Hover over an element |
fill | Type into an input field or select from a dropdown |
fill_form | Fill multiple form fields at once |
type_text | Type text into the currently focused element |
drag | Drag and drop between elements or coordinates |
press_key | Press a key or combination (e.g., Meta+A, Enter) |
upload_file | Upload a file through a file input |
| Tool | Description |
|---|---|
inspect_viewport_meta | Parse the viewport meta tag and validate against iOS best practices (width, zoom, viewport-fit) |
| get_safe_area_insets | Read CSS safe-area-inset values and check whether t
Only the beginning is shown; read the rest in the repo