Two automation workspaces. One product.

Olivia Tool documents and tests your APIs and MCP servers.

API automation turns repositories and endpoint changes into documentation and QA runs. MCP automation turns live servers into tool docs, smoke suites, and bug reports. They are different workflows, handled in one place.

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

2 bugs found with evidence

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.

QA source

Run endpoint QA or MCP tool QA from the documentation Olivia generated, with bugs saved back to the project.

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