Connect your coding agent

If you already work with an AI coding assistant, it knows things Marriska can’t see on its own: your routes, field names, data-testids, and exactly what the current pull request changed. Connect it to Marriska and it turns that knowledge into real tests — authored from code, executed in our cloud, and readable by everyone on the team.

Why route it through Marriska

Your agent could write Playwright code directly. The difference is where the test lives afterwards:

The whole team owns it. A plain-English test is readable by QA, product, and support — not just whoever wrote it.
It runs without infrastructure. Cloud browsers, screenshots, visual regression, schedules, notifications, shareable reports.
It self-heals. Marriska resolves elements by visible text through a locator ladder, so a class rename doesn’t break the suite.
Your code stays yours. The agent reads your repo locally and sends only the finished plain-English steps.

Requirements

A Marriska API key — Settings → API Keys (every plan includes one; paid plans add more).
Node.js 18+ and an MCP-capable assistant (Claude Code, Claude Desktop, Cursor, Codex CLI, or any other MCP client).

Setup

Create an API key

In Marriska, open Settings → API Keys → New key. Copy it — it’s shown once. Treat it like a password: it can create tests and start cloud runs in your organization.

Add the server to your agent

Claude Code:

claude mcp add marriska --env MARRISKA_API_KEY=ak_live_... -- npx -y @marriska/mcp

Any other MCP client (mcp.json, claude_desktop_config.json, Cursor’s MCP settings):

{
  "mcpServers": {
    "marriska": {
      "command": "npx",
      "args": ["-y", "@marriska/mcp"],
      "env": { "MARRISKA_API_KEY": "ak_live_..." }
    }
  }
}

Ask for a test

“Read the checkout flow in this repo, write a Marriska test for the happy path, run it, and show me the result.”

The agent authors the steps, creates the test in your workspace, queues a cloud run, and reports back with the outcome. The test is now in your Tests list like any other — editable, runnable, schedulable.

What the agent can do

Tool	What it does
`list_projects`	Projects in your organization
`list_tests`	Tests with their step counts
`get_test`	One test with its full ordered steps
`create_test`	Create a test from explicit steps
`update_test_steps`	Replace a test’s steps after a code change
`run_test`	Queue a cloud run
`get_run_result`	Status and per-test results

The server also publishes the full step schema as an MCP resource (marriska://step-actions), so the agent learns the format — actions, assertions, wait semantics — without you pasting documentation.

Working well with it

Ask for assertions. “Make sure it verifies the total, not just that the page loads.” A test that only clicks can’t fail.
Point at a diff. “This PR changed the signup flow — update the tests that cover it” is where code-awareness pays off most.
Let QA take it from there. Once the test exists, curating test sets, schedules, and failure triage happens in Marriska — that hand-off is the point.

Self-hosted or staging

Set MARRISKA_API_URL alongside the key (defaults to https://api.marriska.com/api/v1).

API keys — creating, scoping, and revoking keys
Step actions — the same schema the agent reads
Running tests — what happens after a run is queued