Kapptivate for AI agents

AI doesn't just run inside your tests: your coding agent can drive Kapptivate itself. The platform ships two integration surfaces built for agents, an MCP server and a CLI, so the assistant you already work with (Claude Code, Claude Desktop, Codex, GitHub Copilot, Cursor, Gemini) can create tests, launch campaigns, and read results without you switching to the app.

Two ways in

Both authenticate with an API key and carry the same permissions as your account, so an agent can only do what you can do.

What an agent can do

• Create and edit tests: scaffold a test from a template, fill in the steps, validate it, and save it, from a plain-language description of the flow.
• Manage your test base: list, search, archive, and restore tests, inspect their versions, and check what a change impacts.
• Launch campaigns: build a campaign from selected tests, run it, poll the execution, and summarize the failures.
• Get stats: query metrics, compute SLOs, correlate signals, and pull success rates per product or monitor.
• Watch production: create monitors, review incidents, and evaluate alerts.

A typical session reads like a conversation: "run the checkout regression on staging and summarize the failures", "create a monitor for the login test every five minutes", "show last week's success rate for the payments product".

Pick your client

For Claude Code, Claude Desktop, Cursor, and GitHub Copilot, point the client at the MCP endpoint and authenticate with the X-Kapptivate-API-Key header: Connect your AI client has the copy-pasteable configuration for each. Microsoft Copilot Studio and Google Gemini have dedicated integration pages.

Terminal-first agents like Claude Code can also use the CLI directly: install ktm, set KAPPTIVATE_API_KEY, and every platform operation is a command away. The cheat sheet gives an agent the whole surface at a glance.

What's next?