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)
Your coding agent records a demo or tutorial video of your web app.
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.screenbrowser.comRun this in your terminal
claude mcp add --transport http screenbrowser https://mcp.screenbrowser.comPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"screenbrowser": {
"url": "https://mcp.screenbrowser.com"
}
}
}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": {
"screenbrowser": {
"type": "http",
"url": "https://mcp.screenbrowser.com"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mcp.screenbrowser.comMenu names can differ slightly by plan and over time.
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.
The server asks you to sign in before it lists its tools.
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 6, 2026
The registry name was verified against the domain screenbrowser.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 590 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.3.14) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
Narrated demo and tutorial videos of your web app, from a guide or your coding agent.
Ask the agent that knows your codebase for a tutorial video of a feature. It writes the walkthrough in the words your buttons and fields use, Screen Browser records a real browser following it against your deployed app, narrates it, adds the on-screen effects, and the agent hands you the MP4 with a GIF, subtitles and chapters. When the app changes, edit a line and ask again.
That is the first chapter of a 66-second video made from the request *"make a tutorial video of creating a campaign"*. The whole session, from that sentence to the finished video with the exact prompt and every screen along the way, is in the Claude Code guide.
This repository gives your agent two things:
https://mcp.screenbrowser.com.Claude Code, Codex, Cursor or any MCP client can use it. Sign-in happens in the browser; there is no key to paste.
Add this repository as a plugin marketplace and install the plugin:
claude plugin marketplace add screenbrowser/skill
claude plugin install screenbrowser@screenbrowser
The first time the agent reaches for a Screen Browser tool, Claude Code opens your browser: sign in to Screen Browser, approve the connection, and you are done. Nothing to copy. (If it does not prompt, run /mcp and pick screenbrowser → Authenticate.)
Without the plugin system, register the server yourself and copy the skill:
claude mcp add --transport http screenbrowser https://mcp.screenbrowser.com
cp -r skills/screenbrowser ~/.claude/skills/
If your agent cannot open a browser to sign in, create a key under Settings → API keys in Screen Browser and pass it as a bearer token:
claude mcp add --transport http screenbrowser https://mcp.screenbrowser.com \
--header "Authorization: Bearer "
Any MCP client works the same way: Streamable HTTP at https://mcp.screenbrowser.com, OAuth 2.1 with dynamic client registration for interactive sign-in, or Authorization: Bearer .
The skill is a plain SKILL.md in the open Agent Skills format, and the server is standard MCP over HTTP, so the same two pieces work outside Claude Code.
Cursor, VS Code, GitHub Copilot and other Agent Plugins clients — this repository is also an Agent Plugins package (plugin.json, mcp.json, skills/), so install it as a plugin from the repository URL and sign in when the client offers. Cursor without the plugin: add the server to .cursor/mcp.json (or the global one in Cursor settings), click Sign in next to it, and copy the skill into .cursor/skills/:
{
"mcpServers": { "screenbrowser": { "url": "https://mcp.screenbrowser.com" } } }
mkdir -p .cursor/skills && cp -r skills/screenbrowser .cursor/skills/
OpenAI Codex CLI — add the server to ~/.codex/config.toml, sign in once, and copy the skill into Codex's skills folder:
[mcp_servers.screenbrowser]
url = "https://mcp.screenbrowser.com"
codex mcp login screenbrowser
mkdir -p ~/.codex/skills && cp -r skills/screenbrowser ~/.codex/skills/
Anything else (Gemini CLI, Windsurf, a custom agent) — register an HTTP MCP server with the URL the way that tool documents it; a client that supports OAuth will sign you in, one that does not takes the API key as an Authorization: Bearer header. Give the agent skills/screenbrowser/SKILL.md as instructions (paste it, or point the tool's rules file at it). The MCP server itself also carries the guide syntax as a resource and a write-tutorial-guide prompt, so a client with MCP prompts can work without the skill file at all.
Videos can be recorded on the desktop or as a phone or tablet (device: iphone, android, ipad, …), in a phone frame on a vertical 9:16 or widescreen 16:9 canvas or as the bare screen; one run is one device.
Open your app's repository in Claude Code and ask:
Make a tutorial video of creating a campaign.
The agent will check credits, create the project (it will ask you for the deployed URL, a demo user, and the legal attestation), write the guides from your routes and templates, validate them, show them to you, start the run, and give you the video link a few minutes later.
The MCP server also ships a get_guide_instructions tool with the same writing rules, for clients without this skill, a write-tutorial-guide prompt that walks any client through the same flow, and two resources: screenbrowser://guide-syntax and screenbrowser://example-guides.
Everything the plugin does goes to one place: the Screen Browser MCP server at https://mcp.screenbrowser.com, over HTTPS, signed in with your Screen Browser account. The skill itself is instructions for the agent; it runs nothing on your machine and fetches nothing.
What the agent sends to Screen Browser when you ask for a video:
It never sends your source code. The agent reads your repository locally to learn the labels; only the guide text leaves the machine. Nothing is sent to any other service. What Screen Browser keeps, and for how long, is in the privacy policy.
Plans start at $49 a month, sized in minutes of finished video. Checking a guide before recording is free, and a run that fails is not charged. Videos are capped at five minutes. There is no free plan, but the first 100 accounts get 10 free minutes with no card. Current prices are on the pricing page.
plugin.json Agent Plugins manifest (Cursor, VS Code, Copilot, …)
mcp.json Agent Plugins MCP config (the URL; sign-in is OAuth) .claude-plugin/plugin.json Claude Code plugin manifest .claude-plugin/marketplace.json lets this repo act as its own Claude Code marketplace .mcp.json Claude Code MCP server config skills/screenbrowser/SKILL.md the skill skills/screenbrowser/references/ guide syntax reference, worked example examples/chatamatic/ a real auth guide + main guide pair
Plain language, one step per line, naming things as they appear on screen. Screen Browser turns it into the script — the narration, the highlights, the pacing — and resolves each step against the live page:
Go to https://app.acme.test/campaigns
"Let's create a spring promotion." Click "New campaign" Type "Spring promo" into the Name field Click "Save" Confirm text "Campaign created" is visible
Ids and name= attributes are allowed when a step needs precision; class names generated by a build tool are refused. The full reference, including the optional effect directives, is in skills/screenbrowser/references/guide-syntax.md.
The skill carries everything an agent needs to write a guide and run a recording. For anything else — prerequisites, costs, limitations, the API — https://screenbrowser.com/llms.txt is a Markdown index of the public documentation, and https://screenbrowser.com/docs/agents/ is the reference for this integration.
Issues and ideas about the skill are welcome in this repository. Anything about your account or a particular recording: use the contact form at https://screenbrowser.com/contact/.
MIT. Screen Browser itself is a hosted service; this repository contains only the agent-facing skill, configuration and examples.