Projects
A project represents one web application you test with TestVibe. It bundles:
- a base URL — the site your tests run against (overridable per generation/run with
siteUrl), - features — desired behavior in Gherkin, plus their generated Playwright tests,
- files — the test sources and Playwright configurations,
- runs — the execution history with results and artifacts.
Identification
Each project has a public id (a GUID) — this is the id returned by list_projects and the value REST routes take in the path:
/api/v1/ops/projects/7f3c9a4e-2b1d-4e8a-9c6f-0d5b8a1e2f34/features
The CLI and MCP tools are friendlier: testvibe use <id-or-name> sets a default project, and every project-scoped MCP tool takes an optional project argument that overrides it.
Scoping
An API key belongs to a workspace (account). It sees that workspace's projects and nothing else — there is no cross-workspace access, and a key dies when its creator leaves the workspace. See Authentication.
Site URL overrides. A project can have more than one deployment of the app under test (staging, preview environments). Pass siteUrl to generate_feature or run_feature to target one without changing the project's configured URL.