Agent MCP Server

Agent to integrate Playwright with ReportPortal. The agent mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Look through the example-playwright to check out the integration in action.

Its toolset

Everything the assistant can do here goes through one of these:

• apiKey — Conditional
• oauth — Conditional
• Property — Necessity
• tokenEndpoint — Required
• username — Required
• password — Required
• clientId — Required
• clientSecret — Optional
• scope — Optional
• endpoint — Required
• launch — Required
• project — Required

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent's toolset — apiKey, oauth, Property and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Agent.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent mcp server does with a few real requests.