screen-browser

MCP开发工具

提供方 Screen Browser · 包名 skills

开发工具 stdio · 本地进程 OAuth 授权 社区 / 第三方 ClaudeCursorVS CodeCodex
查看接入方式

由 Screen Browser 提供的 MCP 服务器,stdio · 本地进程。

一句话选型结论

按资料字段整理

screen-browser 属于开发工具类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

video tutorial documentation developer%20tools mcp%20server

支持客户端

适用场景

videotutorialdocumentation

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx skills add screenbrowser/skill

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
screen-browser当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方Screen Browser上游标注的维护方 Screen Browser
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时skills · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.8 KB
来自项目仓库与上游目录的原文,未做删改

Screen Browser skill

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:

  • The screenbrowser skill — how to read your codebase and write the two guides Screen Browser
    needs (the login flow and the walkthrough), which effect fits which moment, how to check a guide
    for free before recording, and how to review the video before handing it over.
  • The MCP server configuration — the tools the agent calls: create the project, upload guides,
    check them, start the run, poll it, fetch the video. The server itself is part of your Screen
    Browser account at 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.

Install (Claude Code)

Add this repository as a plugin marketplace and install the plugin:```bash
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:```bash
claude mcp add --transport http screenbrowser https://mcp.screenbrowser.com
cp -r skills/screenbrowser ~/.claude/skills/

With an API key instead

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:```bash
claude mcp add --transport http screenbrowser https://mcp.screenbrowser.com \
--header "Authorization: Bearer <your API key>"


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 `.

### Other agents

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/`:```json
{
  &quot;mcpServers&quot;: {
    &quot;screenbrowser&quot;: { &quot;url&quot;: &quot;https://mcp.screenbrowser.com&quot; }
  }
}
``````bash
mkdir -p .cursor/skills &amp;&amp; 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:```toml
[mcp_servers.screenbrowser]
url = "https://mcp.screenbrowser.com"
``````bash
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&#x27;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.

## Use

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&#x27;s repository in Claude Code and ask:

&gt; 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 `write-tutorial-guide` prompt that walks any client through the same
flow, and two resources: `screenbrowser://guide-syntax` and `screenbrowser://example-guides`.

## What your app needs

- A **demo user** that signs in with email and password: no OAuth, no 2FA, no captcha. Seed it with
  realistic data.
- The deployed URL to record (staging is fine) and every host the app talks to (API subdomain,
  auth provider, CDN).
- Confirmation that you are allowed to record the app (yours, a client&#x27;s with permission, or an
  internal tool).

## What it sends, and where

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:

- the project&#x27;s settings: your app&#x27;s URL, the hosts it talks to, the sign-in check, narration
  language and voice;
- the guides it writes from your code: plain sentences naming buttons and fields as they appear on
  screen. Read them before they are saved; the agent shows them to you;
- the demo user&#x27;s credentials, as project variables. Screen Browser stores them encrypted, uses
  them only to sign in during a recording, and never returns them through any tool. Values you
  give the agent pass through its conversation; to keep them out of chat, set them on the
  project&#x27;s page in the Screen Browser dashboard instead;
- run commands: start, poll, cancel, and, only if you agree, a failure report with the recorder&#x27;s
  screenshot and logs of a run that failed on Screen Browser&#x27;s side.

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.

## What it costs

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. Current prices are on the pricing page.

## Layout```
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

What a guide looks like

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 &quot;Let&#x27;s create a spring promotion.&quot; Click &quot;New campaign&quot; Type &quot;Spring promo&quot; into the Name field Click &quot;Save&quot; Confirm text &quot;Campaign created&quot; 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.

Documentation index for AI agents

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.

Support

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/.

License

MIT. Screen Browser itself is a hosted service; this repository contains only the agent-facing
skill, configuration and examples.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
screen-browser 怎么安装?

在客户端按下面的安装命令接入:npx skills add screenbrowser/skill。对应的包名是 skills。装完在客户端配置里引用同一个包或端点。

screen-browser 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

screen-browser 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

screen-browser 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

screen-browser 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

screen-browser 能提供哪些能力?

资料显示能力标签包括 video、tutorial、documentation、developer%20tools、mcp%20server。具体工具清单以官方文档为准。

screen-browser 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

screen-browser 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。