Vera’s MCP server: end-to-end testing for any MCP client

Vera exposes its projects, tests, runs and AI repair as an MCP server, so any MCP client can run a test, read why it failed, propose a fix and apply it with your approval. The endpoint is stateless Streamable HTTP behind a workspace-scoped bearer token.

What comes across

  • The endpoint is POST /api/mcp over Streamable HTTP, stateless — there is no session to manage.
  • Auth is a vera_… bearer token — the same tokens the CI API uses — scoped to one workspace.
  • It is the free plan's floor (mcp-basic): a free workspace can mint a token and use it here.
  • run_test starts a run and returns immediately; wait_for_run returns the status and per-step results, with console and network tails on a failure.
  • get_failure_details returns the failed steps, errors and artifact paths — the debugging payload.
  • inspect_page and verify_selector check selectors against the live page with no AI call.
  • suggest_fix only proposes; apply_repair requires confirm=true and records a repair audit.

What does not

  • AI tools — suggest_fix, generate_tests, generate_repro_test — are metered to the workspace's AI usage and need its AI setup.
  • Plan-gated tools keep their plan: chains need Team, and the app-change radar needs Pro.
  • generate_repro_test blocks for up to about four minutes and sends no progress notifications; raise the client timeout rather than retrying.
  • A token cannot read or change organization settings, and it can never create a project.

How to set it up

  1. Mint a token under Settings → CI Tokens. It is shown once.
  2. Point the client at https://your-vera-host/api/mcp with an Authorization: Bearer vera_… header.
  3. With the claude CLI: claude mcp add --transport http vera https://your-vera-host/api/mcp --header "Authorization: Bearer vera_…".
  4. In a committed config file, write "Bearer ${VERA_TOKEN}" and export the token in your environment instead.

Questions

Which MCP transport does Vera use?

Streamable HTTP, stateless, at POST /api/mcp. There is no session to manage.

Can an MCP token see another workspace?

No. Every tool is scoped to the token’s workspace; a token for one organization can never see or touch another’s data.

Does using Vera over MCP need a paid plan?

No. MCP is the free plan's floor. Some tools keep their own plan gate, and the separate CI API needs Pro.

Read more

Start free