
Lastest
io.github.las-team由 GitHub 账号 las-team 发布v0.3.7更新于 Oct 24, 2026
Run visual regression tests, review diffs, and manage baselines on a Lastest instance.
概览
将 AI 助手连接到 Lastest 实例,用于运行视觉回归测试、查看截图差异并批准基线。
- 可以做什么
- 列出并管理仓库、功能区域、测试、构建和后台任务,包括用 AI 创建测试以及更新测试运行时设置和初始化配置。触发测试运行并读取运行结果、覆盖率统计和 QA 摘要。查看视觉差异并逐条或批量批准、拒绝基线,包括验证阶段的逐层审批。管理共享认证的存储状态和可复用的初始化脚本。发布、列出和撤销构建与测试的公开分享链接。用 AI 修复失败的测试,并获得应用代码修复建议。
- 适用场景
- 适合在 Lastest 实例上进行视觉回归测试的团队,让助手触发运行、排查截图差异、批准基线并获取 QA 或覆盖率报告,而无需切换到网页界面。
- 运行要求
- 需要 Node.js 18+ 和可访问的 Lastest 实例。stdio 包通过实例 URL 和在 Lastest 界面创建的 API 密钥启动,密钥以命令行参数传入。也可改用实例上的远程 Streamable HTTP 端点,支持 API 密钥或 OAuth 2.1。
安装
在 SourceWeft 中
- 打开 控制台中的 Lastest,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
@lastest/mcp-server
[npm version] [npm downloads] [License] [GitHub stars]
MCP server for Claude Code, Cursor, Windsurf, Cline, and Claude Desktop. Lets AI agents run visual regression tests, review screenshot diffs, and approve baselines on a Lastest instance through the Model Context Protocol.
Quick start
Generate an API key in the Lastest UI: Settings → Runners & API Access → Create API Key (shown only once). The server speaks MCP over stdio — wire it into any compatible client below.
Compatible clients
Any MCP-compliant client that can launch a stdio server with arguments works.
Install — Claude Code
Verify with claude mcp list.
Install — Claude Desktop / Cursor / Windsurf / Cline
Add to claude_desktop_config.json, ~/.cursor/mcp.json, or your client's MCP config:
Restart the client.
What an agent can do
- List repositories, tests, functional areas, builds, and active jobs
- Create AI-authored tests from a URL or natural-language prompt
- Update or delete tests and functional areas
- Self-configure test runtime:
playwrightOverrides,diffOverrides,stabilizationOverrides, viewport, setup wiring - Manage shared auth: storage states (Playwright
storageState()blobs) and reusable setup scripts - Trigger test runs (optionally
forceVideoRecording) and read run results - Inspect visual diffs and approve / reject baselines individually or in bulk
- Heal failing tests with AI based on the latest run
- Publish, list, and revoke public-share links for builds and tests
- Read and update repo-level Playwright settings (browser, viewport, timeouts, parallelism, stabilization)
- Drive the Verify phase: Change Map, step comparisons, per-layer approvals
- Pull QA summaries, build review reports, and coverage stats
Tools exposed
The server registers 20 MCP tools (all prefixed lastest_). Every tool returns a structured { status, summary, actionRequired?, details } payload.
Pure CRUD operations are consolidated into resource tools that take an action (or scope) discriminator; workflow verbs stay as standalone tools.
Resource tools (action-dispatched)
Workflow verbs (standalone)
Self-configuring tests
lastest_test (action: "update") accepts a full override surface so an agent can shape a test without touching the UI:
- Setup wiring —
setupTestId(use another test as setup, takes precedence) orsetupScriptId, plussetupOverrides/teardownOverridesblocks to inject/skip default steps (test|script|storage_state). - Runtime overrides —
playwrightOverrides(browser, navigation/action/selector timeouts, error modes,baseUrl, cursor speed),viewportOverride,diffOverrides,stabilizationOverrides. - Lifecycle —
quarantined,executionMode(procedural|agent).
Pass null to any override block to clear it. The API validates each referenced id is in the same repo before persisting.
Migration — tool consolidation (v0.3.x)
The tool surface was consolidated from ~56 discrete tools to ~21 by folding pure
CRUD into the resource tools above. This is a breaking change for scripts
that called the old per-operation tool names. The workflow verbs and the
QuickStart chain (lastest_quickstart → lastest_quickstart_status →
lastest_publish_share) kept their names and signatures. Map any removed names
as follows:
If you need the old names temporarily, pin a 0.2.x release of this package
while you migrate.
CLI
The process communicates with the host client over stdio.
Requirements: Node.js 18+ and a reachable Lastest instance.
Remote (Streamable HTTP)
Most people want the endpoint your Lastest instance already serves:
It speaks Streamable HTTP and accepts either an API key or an OAuth 2.1
connection, so an agent platform that only knows a URL (Salesforce Agentforce,
ChatGPT, Claude web) can connect on its own — it discovers the authorization
server from the WWW-Authenticate header, registers itself, and sends you
through a consent screen. OAuth connections get a read or write subset
of the tools; deleting things, revoking shares and publishing public links stay
behind your own API key.
Run this package as its own HTTP server when you want the MCP endpoint on a separate host or port:
This mode is API-key only; there is no OAuth in the standalone process.
Access levels
--access-level (and, on /api/mcp, the OAuth scope) picks the tool surface:
Tools are filtered at registration, so a restricted connection never sees an action it cannot call.
Authentication
The server authenticates against Lastest's REST API (/api/v1/*) with a Bearer token. Manage and revoke keys from Settings → Runners & API Access in the Lastest UI.
Troubleshooting
Local development
Used with
- Lastest — visual regression testing platform with screenshot diffs and AI test authoring
- @lastest/runner — self-hosted runner so AI-triggered tests execute on your infra
- Model Context Protocol — open standard powering tool use in Claude, Cursor, Windsurf, and others
Links
- Homepage: https://lastest.cloud
- GitHub: https://github.com/las-team/lastest
- Wiki: https://github.com/las-team/lastest/wiki/MCP-Server
- Issues: https://github.com/las-team/lastest/issues
- npm: https://www.npmjs.com/package/@lastest/mcp-server
License
FSL-1.1-ALv2 — see LICENSE.
来源:packages/mcp-server/README.md,提交 d734cce
工具
0版本历史
1- v0.3.7最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。