Three automation workspaces. One product.

Olivia Tool documents and tests your APIs, MCP servers, and end-to-end flows.

Run a flow once and Olivia turns it into a Playwright test, commits it to your repo, and heals it when the app changes. Plus API automation for endpoint docs and QA, and MCP automation for tool docs, smoke suites, and bug reports.

Start with Olivia Open workspace

Olivia workspace

Live outputs

API Docs + QA

GET /users

POST /orders

QA run: 15 tests

MCP Docs + QA

search_docs

create_ticket

Smoke: 8 cases

E2E Recorder + Playwright

New

Run oncecheckout.spec.tsCommitted

2 bugs found with evidence

New — E2E Automation

Run it once. Olivia writes the Playwright test, commits it, and keeps it green.

No more hand-writing brittle end-to-end tests. Walk through a flow a single time and Olivia generates a real Playwright spec with AI, commits it into your repo, and self-heals it as your app evolves.

Run the flow once

Click through the journey you care about in the recorder, or upload a quick demo video. No selectors, no boilerplate.

AI writes the Playwright test

Olivia turns what you did into a clean, readable Playwright spec with stable locators and assertions.

Commit straight to your repo

The test lands in your project structure with a commit, matching your existing Playwright config and conventions.

It heals when the app changes

When selectors drift or flows shift, Olivia repairs the test instead of letting it fail silently.

Try E2E automation Works with your existing Playwright setup.

API Automation

For repositories, endpoints, and API QA.

This side of Olivia is built around code repositories. It scans API routes, generates endpoint documentation, keeps docs aligned with pull request changes, and runs QA against documented endpoints.

Endpoint documentation
Methods, paths, params, bodies
Responses and examples
Repo backfills
PR change updates
Endpoint QA runs

MCP Automation

For servers, tools, schemas, and tool QA.

This side of Olivia is built around running MCP servers. It connects to the server, discovers tools, documents each tool, captures sample behavior, creates smoke suites, and tracks tool-level bugs.

Tool documentation
Input schemas and required args
Sample arguments
Live tool responses
Smoke suites per project
Tool-level bug reports

QA Layer

Testing is not an afterthought. It is generated from what Olivia understands.

API QA and MCP QA do not run the same way. Olivia keeps the workflows separate: endpoint tests for APIs, tool execution tests for MCP, shared reporting for bugs.

Smoke

Fast checks for the paths that must work

For APIs, Olivia tests generated endpoint behavior. For MCP, Olivia generates and runs tool smoke suites with real arguments.

Regression

Reusable coverage for behavior you already trust

Turn documented behavior into repeatable checks so the next release does not quietly break what worked yesterday.

Bugs

Failures written like engineering tickets

Each issue includes the target, scenario, severity, evidence, and recommendation so a developer can fix it without decoding a vague report.

Workflow

Three sources. Three outputs. One review surface.

Olivia is not only a docs generator. It is a workspace for turning engineering systems into readable documentation, runnable checks, and actionable bug reports.

API source

Connect GitHub, select a repository, run a backfill, or let pull request changes update endpoint docs.

MCP source

Connect an MCP server over stdio, HTTP, or SSE and let Olivia inspect available tools and schemas.

E2E source

Record a browser flow once and Olivia generates a Playwright test, commits it to your repo, and heals it over time.

API docs

Generated from repositories, endpoint scans, and pull request changes.

MCP docs

Generated from connected servers, tools, schemas, and sample responses.

Bug evidence

Generated from QA runs with severity, evidence, and recommendations.

Built for teams shipping APIs, MCP servers, and integrations

Separate workflows. Shared visibility.

API teams get endpoint docs and API QA. MCP builders get tool docs and MCP QA. Engineering leaders get a single place to see documentation, test coverage, and bugs.

Get Olivia Tool