Skip to content

Endform MCP server

The Endform CLI includes a local Model Context Protocol (MCP) server. It gives AI coding agents tools for analyzing historical test data and debugging a Playwright test on Endform’s remote infrastructure.

Authenticate the Endform CLI first:

Terminal window
npx endform@latest login

Then add Endform as a local MCP server in your AI coding tool:

Run this command from your project directory:

Terminal window
claude mcp add --transport stdio --scope local endform -- npx -y endform@latest mcp

Restart the AI coding tool or reload its MCP servers after changing the configuration. The server must run from your project so that its debugging tools can locate your Playwright configuration and tests.

These tools query the same suite and test history that powers the Endform dashboard. See Investigate test history with AI for example conversations.

Lists the organizations available to the active Endform login. Agents can use it when another tool asks for organization selection.

Compares run counts, pass rates, and durations over time. Results are returned as time series with count, percent, or seconds as the unit.

ParameterTypeDescription
datasetsuite-runs or test-runsAggregate complete suite runs or individual test runs.
metriccount, pass-rate, or average-durationMetric to calculate.
groupByoutcome, branch, test, or projectOptional grouping. Suite runs cannot be grouped by test or project.
wherestringOptional filter expression, such as testRun.outcome = fail, branch = main.
periodstringPositive integer followed by H, D, W, or M. Defaults to 7D.
endingAtISO 8601 stringOptional end of the time window. Defaults to the current time.

Returns concrete suite-run or test-run executions matching a filter. Test-run samples include the test identity, project, outcome, duration, and every attempt in chronological order. Attempts may contain an error message, error location, and otelTraceId.

ParameterTypeDescription
datasetsuite-runs or test-runsReturn complete suite runs or individual test runs.
wherestringOptional filter expression, such as testRun.testAttemptsCount > 1.
periodstringPositive integer followed by H, D, W, or M. Defaults to 7D.
endingAtISO 8601 stringOptional end of the time window. Defaults to the current time.
limitnumberNumber of newest records to return. Defaults to 10; maximum 50.
cursorstringOptional nextCursor from an earlier response for pagination.

Filters are comma-separated clauses. String fields support operators such as =, !=, ^=, $=, ~=, !~=, in, and !in; numeric fields support comparisons such as >, >=, <, and <=. The tool’s input schema contains the complete field and operator reference.

Returns raw OpenTelemetry trace data for a test attempt. The trace can show Playwright actions, network activity, timing, and other spans recorded while that attempt ran.

ParameterTypeDescription
traceIdstringThe otelTraceId returned by query_samples.

These tools let an AI agent pause inside one Playwright test and inspect or interact with its live browser state. See Debug tests with AI for example conversations.

Starts a remote debug session and pauses at a checkpoint inside exactly one matching test. Startup can take a few minutes. The response includes a sessionId, the checkpoint location, result and log paths, and an initial ARIA snapshot of the page.

ParameterTypeDescription
testFileFiltersstring[]Playwright-style regular expressions matched against absolute test paths. A filter may include a declaration line, such as tests/checkout.spec.ts:47.
grepstring[]Include tests whose full title chain matches these regular expressions.
grepInvertstring[]Exclude tests whose full title chain matches these regular expressions.
projectstring[]Include tests from these Playwright projects.
linenumber1-based source line to pause before. Defaults to the first statement in the test body.
configstringOptional Playwright configuration file or test directory.

The selection must resolve to one test. Sessions end automatically after 15 minutes.

Runs JavaScript inside the paused test’s scope. The code can use await and test fixtures such as page. The agent can call this repeatedly to inspect locators, read application state, interact with the page, or create screenshots.

ParameterTypeDescription
sessionIdstringSession returned by debug_test_start.
codestringJavaScript to evaluate at the checkpoint.

Each call returns standard output, standard error, an exit code, a fresh ARIA snapshot, and paths to newly created artifacts. A non-zero exit code means the code threw; the session remains paused.

Returns the current session state: starting, paused, running, ended, or stale. A paused response includes a fresh ARIA snapshot.

ParameterTypeDescription
sessionIdstringSession returned by debug_test_start.

Stops a debug session and cleans up its local and remote resources. Agents should call it when debugging is complete rather than waiting for the 15-minute limit.

ParameterTypeDescription
sessionIdstringSession returned by debug_test_start.