Browser Use
by 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.
Computer or cloud★ 120,087MITUpdated 18 days ago
Install
Screenplay
Overview
Description from the maker (original English)
Beautiful screen recordings of any website or desktop app, scripted by your agent.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Web & browsers
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
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": {
"agent-screenplay": {
"command": "npx",
"args": [
"-y",
"agent-screenplay",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add agent-screenplay -- npx -y agent-screenplay mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-screenplay": {
"command": "npx",
"args": [
"-y",
"agent-screenplay",
"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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-screenplay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agent-screenplay",
"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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account gmpetrov, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Web & browsersi
- More stars than 0% of the other 1379 servers in this category
- Published to the registry more recently than 88% of the other 1379 servers in this category
- Basic checks equal to or better than 100% of the other 1379 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Screenplay safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 4 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Alternatives
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
Chrome DevTools MCP
by ChromeDevTools
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Runs on your computer★ 54,821Apache-2.0Updated 16 days ago
Install
MCP Server Browser
by bytedance
MCP server for browser use access
Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
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.
Screenplay
https://github.com/user-attachments/assets/dd9898da-4900-4a91-8620-57a860c46093
Create beautiful screen recordings with one prompt. Any website, yours or someone else's, or any desktop app. Works with Claude Code, Codex, Cursor and any MCP client.
Ask your agent: *"Make a video that shows how human handoff works"*. The agent explores the site or app and writes a short scenario; Screenplay plays it in a browser (or a desktop app), films it, and edits the video like Screen Studio would: smooth cursor, automatic zooms that follow the action, click effects, callouts, spotlight, captions, title cards, and an optional voice-over.
Screenplay contains no AI and needs no model key: your agent does the thinking, Screenplay does the filming and editing.
Install
npx agent-screenplay initThe npm package is agent-screenplay; installed globally (npm i -g agent-screenplay), its command is screenplay.
init downloads Chromium (once), adds the Screenplay MCP server to the agents it finds (Claude Code, Codex, Cursor), and installs the guide that teaches them to make good videos. Restart your agent after it.
Use it
In Claude Code, type /screenplay and say what you want:
/screenplay Make a 30-second walkthrough of https://askli.co/screenplay Film how to invite a teammate in our app, with a French voice-over
In Codex, Cursor or any agent with the MCP server, just ask: *"Make a screen recording of …"*. The agent explores the site, asks whether you want a voice-over, writes the scenario, films it, checks the storyboard and gives you the MP4. To change the look afterwards: npx agent-screenplay style .
Without MCP, any agent that can run commands can use the CLI directly:
npx agent-screenplay guide # how to write a good scenarionpx agent-screenplay check demo.json # plays the steps fast, without filming npx agent-screenplay record demo.json # films and edits → demo.mp4 + demo.storyboard.png npx agent-screenplay render demo.json # re-edits the last take (style, zoom, text, voice) without filming
Requirements: Node 20+. ffmpeg and the drawing library ship with the package.
A scenario
{"url": "https://app.example.com/inbox", "style": { "background": "dawn" }, "steps": [ { "title": "Human handoff, in one click", "subtitle": "New in 2.4" }, { "click": "text=Camille Laurent", "say": "When the AI agent gets stuck, the conversation lands in your inbox." }, { "callout": "role=button[name='Take over']", "text": "Take over from the AI agent" }, { "click": "role=button[name='Take over']", "say": "One click, and the conversation is yours." }, { "type": "Hi Camille, I'm on it.", "into": "placeholder=Write a reply…" }, { "click": "role=button[name='Send']" }, { "highlight": "text=Assigned to you", "text": "Your teammates see it's yours" }, { "end": "Available today on every plan" } ] }
- Targets name elements the way people see them:
text=…,role=button[name='…'],label=…,placeholder=…,testid=…,css=…(web only),at=x,y(desktop apps without accessible elements only). - Actions:
goto,click,type,press,hover,scroll,select,wait,pause. - Direction:
titleandendcards,callout(a bubble pointing at an element),highlight(spotlight),zoomTo, and on any stepsay(caption and voice),zoom,hold. - Style: background preset (soft light gradients:
dawn,iris,citrus,apricot,coral,blaze,cloud,glacier,tide,meadow), your own gradient, a color or an image; padding, corner radius, shadow, the cursor (arrowby default, a rounded arrow in the accent color;macos,dot) and its click effect (rippleby default;rays,confetti,sparkle), maximum zoom, browser frame, accent color. See Style. - Output: 1920×1080 at 30 fps by default; any size up to 4K, 24 to 60 fps, optional GIF.
The full format is the JSON schema in schema/scenario.schema.json (npx agent-screenplay schema), and the agent guide in skills/screenplay/SKILL.md. Examples are in examples/.
check and record really perform the steps (a "Send" click sends): point scenarios at a demo account or a staging environment.
Style
Set the look by eye: npx agent-screenplay style demo.json opens an editor in your browser, on a frame of the last recording. Pick a gradient (or make your own), a color or an image (drop it on the page), set the padding, corners and shadow, then save to this video or to all videos, and render without filming again.
"All videos" writes screenplay.config.json, which applies to every scenario in its folder and below; a scenario's own style wins, setting by setting. The same settings by hand:
{"style": { "background": { "gradient": ["#0ea5e9", "#6366f1"], "angle": 135 }, "padding": 96, "radius": 20, "shadow": true } }
Title and end cards (title and end steps) are off by default: turn them on with "cards": true, or with the switch in the editor.
background is a preset name (dawn by default; earlier presets such as aurora or ocean still work), a color ("#0f172a"), an image path (relative to the file that sets it), or { "gradient": [2 to 4 colors], "angle": degrees }.
Signing in
npx agent-screenplay login https://app.example.comopens a browser window: sign in, then close the window. The session is saved to.screenplay/auth.json(while you go, and when the window closes; Enter in the terminal works too). Use it with"auth": { "storageState": ".screenplay/auth.json" }. Keep that file out of git.- Bot checks (Cloudflare's "Just a moment…"): Screenplay's browser presents itself as an ordinary Chrome, so the checks that need no person pass by themselves. When a site asks a person to prove they are human,
checksays so: runloginon that site, pass the check in the window, close it, and setauth.storageState. Some sites ask again on every visit; those cannot be filmed automatically. - Agents without a screen can sign in with steps:
{ "type": "${EMAIL}", "into": "label=Email" },{ "type": "${PASSWORD}", "into": "label=Password", "secret": true }.${VAR}is read from the environment;secretmasks the text in captions and logs.
Voice-over
Off by default. Turn it on per scenario:
"voice": { "enabled": true, "language": "fr" }Each step's say is spoken, and the video waits for each sentence to finish, so the voice sets the pace. Three ways to get the voice:
- [Cartesia](https://cartesia.ai): set
CARTESIA_API_KEY. - [ElevenLabs](https://elevenlabs.io): set
ELEVENLABS_API_KEY. When both keys are set, Cartesia is used unless"provider": "elevenlabs". - Your own audio files, with no key: give a step
"audio": "voice/02.mp3"(MP3, WAV, M4A…), for instance lines you generated in ElevenLabs' or Cartesia's web app, or with a local TTS model (Piper, Kokoro…) that your agent runs for you. The agent can write the narration for you, one line per step, ready to paste there. Adding audio needs no new filming:render.
Narration is cached: re-rendering with unchanged text costs nothing. voice.id picks another voice, voice.speed its pace. Without voice, say still shows as a caption.
Desktop apps
Use "app": " " instead of "url". The steps are played through the operating system's accessibility APIs by agent-desktop (installed with Screenplay), and the window is filmed with ffmpeg without the system cursor; the editing is the same as for websites.
| Needs | |
|---|---|
| macOS | Allow your terminal or agent app in System Settings → Privacy & Security → Screen Recording and Accessibility |
| Windows | Nothing |
| Linux | An X11 session with the AT-SPI accessibility bus (standard on GNOME). Wayland is not supported: it blocks screen capture and synthetic input by design |
Desktop recordings need a real screen: they cannot run in a headless container. Websites can.
While Screenplay drives the computer, a pill at the top of the screen says so ("Screenplay is recording", or "rehearsing" during a check), with a Stop button that ends the run at once. The pill is left out of the capture, so it is never in the video. macOS and Windows; SCREENPLAY_INDICATOR=0 turns it off.
The whole screen
"screen": true films the whole main screen instead of one window, for videos that go from one app to another or use the menu bar. { "open": " " } launches an app or brings it to the front, a step's "app" acts in another app, and "surface": "menubar" (or menu, sheet, popover, alert) finds elements outside the app's window. Everything on screen is filmed, desktop icons and notifications included: tidy the screen first; on macOS "hideOthers": true hides the other apps.
How it works
scenario.json ──▶ play + film ──────────────────▶ take (frames + timeline of actions)web: Playwright, headless Chromium │ desktop: agent-desktop + ffmpeg ▼ edit: time remap (long waits sped up), camera (spring zooms), cursor path, overlays, captions, voice track │ ▼ draw each frame (Skia) → ffmpeg → MP4
Screenplay knows exactly where and when each click happens, and the box of every element it acts on, so zooms are framed on the element instead of guessed from mouse movement. The cursor is drawn during editing, along a smooth human-like path.
Development
npm installnpm run build npm test # unit tests npm run test:e2e # records a real scenario in headless Chromium and talks to the MCP server
Releasing
npm version patch --no-git-tag-version # or minor / major; also updates src/version.tsMerge that change, then tag the commit on main:
git tag v0.1.4 origin/main && git push origin v0.1.4The tag starts .github/workflows/release.yml. It checks that the tag matches the version and is on main, runs the tests, publishes to npm (with provenance) and creates the GitHub release with notes from the merged pull requests. A version like 0.2.0-beta.1 goes to npm's next tag. Creating a release in GitHub's UI with a new tag works too.
examples/demo-app is a small web app for trying scenarios; examples/desktop-app/notes.py is a GTK app for desktop recording on Linux.
License
MIT. Bundled: Inter (SIL Open Font License), ffmpeg through ffmpeg-static (GPL), agent-desktop (Apache-2.0).