Vera

Vera for Claude Code: check UI changes in a real browser

Claude Code can drive Vera through its MCP server: run a check of a change in a real browser as a captured auth role, read why a run failed, and propose a repair. One command, npx vera-agent init, registers the server and adds Vera's instructions for the agent, and Vera refuses to rewrite a test until the call carries confirm=true.

What comes across

  • npx vera-agent init registers a vera MCP server for the repository — privately by default, or in the committed .mcp.json with --mcp-scope project.
  • init also writes Vera's agent-instructions block into AGENTS.md or CLAUDE.md, alongside the project link in .vera/config.json.
  • Checks run as a captured auth role, so the logged-in app is testable without credentials entering the agent’s context.
  • Every run leaves a row, artifacts and a link a person can open.
  • apply_repair refuses to edit a test unless the call carries confirm=true.
  • The MCP surface is the free plan's floor, so a free workspace can mint a token and use it.

What does not

  • The Vera plugin for Claude Code — the vera-testing skill and the six /vera commands — is not in a public plugin marketplace yet. npx vera-agent init connects the same MCP server, without the slash commands.
  • Generating and repairing tests need the workspace's own AI key; running, inspecting, scenarios and failure details work without one.
  • A deployment that runs tests on a queue worker cannot run an unsaved step list; save it as a test, or point the environment at your own vera-agent.
  • One ad-hoc scenario runs at a time per workspace, under an hourly cap an admin sets.
  • Vera is not a general browser-automation tool. To read a public page, a plain browser tool is lighter.

How to set it up

  1. Mint a personal token under Settings → CI Tokens. It is shown once.
  2. In your repository, run npx vera-agent init --url https://your-vera-host --token vera_… to link the repo and register the MCP server.
  3. For the whole team, run init with --mcp-scope project: the vera entry goes into the committed .mcp.json with a VERA_TOKEN placeholder instead of the secret, and each developer exports their own token.
  4. Ask Claude Code to try a change once: run_scenario runs the steps in a real browser as an auth role and saves nothing, and save_scenario_as_test keeps a check worth keeping.

Questions

Is Vera for Claude Code free?

The MCP surface is the free plan's floor, so a free workspace can mint a token and connect Claude Code. Some tools are plan-gated, such as chains on Team.

Will Claude Code change my tests without asking?

Not an existing one. Vera refuses to rewrite a test, apply a repair or change an issue unless the call carries confirm=true, so the first call is only a review. Creating a new test needs no confirmation.

Can Claude Code test my app on localhost through Vera?

Yes, when the environment points at an enrolled vera-agent, which runs the steps on your own machine and can reach localhost.

Does it need an AI key?

Only for generation and repair. Inspecting pages, running tests and scenarios, and reading failure details work without the workspace's own key.

Read more

Start free