MCP server
Connect AI assistants to Kapptivate's MCP server to run tests, manage monitors, query metrics, and triage incidents securely.
The Kapptivate MCP server gives AI assistants direct, governed access to your platform. Point an MCP client at your endpoint, authenticate, and the model can discover tests, run campaigns, query metrics, manage monitors, and triage incidents through tools that map one-to-one to Kapptivate.
Use it to turn intent into action: "run the checkout regression on staging and summarize the failures", "create a monitor for the login test every five minutes", or "show last week's success rate for the payments product".
How it works
The server speaks the Model Context Protocol, the open standard for connecting assistants to tools. Kapptivate hosts it at:
https://mcp.kapptivate.com/mcp
Use that one if you sign in at app.kapptivate.com. Sign in elsewhere and your endpoint carries the name of your environment, taken from the first part of the address you sign in with:
https://mcp.kapptivate.com/t/<environment>/mcp
So acme.kapptivate.com becomes https://mcp.kapptivate.com/t/acme/mcp. Connect your AI client walks through it, and everything else on this page reads the same either way.
Your client authenticates every request with the X-Kapptivate-API-Key header, or with a browser sign-in. The session carries the same permissions as your Kapptivate account, so the assistant can only do what you can do.
Your API key grants the same access as your account. Treat it like a password: never commit it to a repository or paste it into a shared chat.
Depending on which AI tool you use, granting it access could expose your data. Review its permissions carefully before authorizing it.
What you can do
What's next?
Last updated on