Lastest
Drive visual regression runs, inspect diffs, and approve baselines on your self-hosted Lastest instance from the agent.
Overview
Lastest MCP is an MCP server for the Ship phase that runs visual regression tests and baseline reviews against your Lastest instance.
What is this MCP server?
- MCP bridge to a Lastest instance for visual regression workflows
- CLI args --url and --api-key (Runners & API Access) required on stdio npm @lastest/mcp-server v0.2.2
- Review visual diffs and manage baselines without leaving the agent
- Pairs with self-hosted Lastest from las-team/lastest monorepo
- MCP server package version 0.2.2
- Two required runtime arguments: --url and --api-key
- Stdio transport via npm identifier @lastest/mcp-server
Community signal: 8 GitHub stars.
What problem does it solve?
Visual regressions slip through when only humans click through staging and the agent cannot see Lastest results.
Who is it for?
Small teams with a running Lastest server who want agent-driven VRT during PR and pre-launch checks.
Skip if: Builders without a Lastest deployment or who only need unit or API tests.
What do I get? / Deliverables
After configuring --url and --api-key, the agent can trigger runs, surface diffs, and help you accept or reject baselines from the IDE.
- Agent-triggered visual regression test runs on your Lastest instance
- Diff review and baseline management actions via MCP tools
Recommended MCP Servers
Journey fit
How it compares
Self-hosted visual regression MCP, not a generic Playwright skill or cloud-only Percy wrapper.
Common Questions / FAQ
Who is lastest for?
Frontend-focused solo builders and tiny teams already using Lastest who want MCP control from Claude Code or Cursor.
When should I use lastest?
Use it in ship/testing before releases or after UI refactors when screenshot baselines must be updated deliberately.
How do I add lastest to my agent?
Register @lastest/mcp-server with stdio, pass --url for your instance and --api-key from Lastest settings, then reload MCP tools.