Now in beta

AI-Supported Testing,
Grounded in Your Requirements.

Connect your coding agent to BesTest over MCP. It reads your requirements and coverage, generates automated tests in Playwright or any language, and syncs results back - while your code stays in your own repo.

Now in closed beta, access granted per user. Request access →

Two MCPs, one conversation

The Atlassian MCP handles Jira.
The BesTest MCP handles testing.

Every vendor brings their own MCP to the party. You add both to your agent once, then watch what one sentence sets in motion.

You say

What is our coverage on the checkout requirements, and which gap is riskiest?

Your AI agentany MCP client
Claude CodeCursorGitHub CopilotWindsurfAtlassian Rovo+ more
Atlassian ships thisAtlassian MCP

Officially the Rovo MCP Server. Most people say "the Jira MCP".

Work itemsConfluenceTeamwork Graph

idle - no Jira call needed here

We ship thisBesTest MCP

Closed beta, access granted per user. GA soon.

RequirementsCoverageTest casesCycles & runsConfiguration
list requirementscheckout folder, 3 requirements
get coveragesignificance-weighted

What lands

Coverage at 71%, with the riskiest gap named rather than just the lowest one.

PHX-REQ-204Checkout flowCovered
PHX-REQ-311Fraud screeningRiskiest gap
PHX-REQ-207Refund within 14 daysCovered

Riskiest is not simply lowest: significance weights complexity times impact.

Read the what-is-MCP guide

Plan in Jira. Test in BesTest. One conversation.

Illustrative conversation · the BesTest MCP is in closed beta

How it fits Rovo

Through your agent, BesTest pairs with Atlassian’s Teamwork Graph: their MCP brings the org-wide context, ours brings the testing depth.

Now in beta

Now Supporting Your AI Agents
Requirements-Aware Test Automation

BesTest already links your requirements, test cases, and execution. Now your CI pipelines and coding agents can read and update all of it through our REST API and MCP server, with your testing context as the source of truth.

01

Connect

Add a development key in your BesTest project settings. Your IDE agent connects over our MCP server, scoped to exactly the Jira permissions you already have. Agents only ever see what you are allowed to see.

02

Understand

Agents pull requirements, test cases, test cycles, and coverage to understand what actually needs testing, grounded in your real project context instead of guesswork.

03

Act

Generate Playwright and automated test cases from requirement context, then push execution results back from CI through the REST API. Manual and automated land in one coverage picture.

MCP ServerREST APICI/CD pipelinesPermission-aware
Pairs with the Atlassian MCP

Add Atlassian's own MCP alongside ours: theirs brings Jira, Confluence, and Teamwork Graph context, ours brings requirements, test cases, and coverage. Your agent reasons over both in one conversation, with permissions intact.

Now in closed beta, access granted per user. Request access →

Governance first

Agents write the tests. You stay in control.

Acts as you

Everything the agent reads or writes stays inside your own Jira permissions.

Granted per user

Beta access is enabled per person, never site-wide by surprise.

Hardened before GA

Closed beta while we harden security - the MCP your security team can approve.

Request beta access

The request form asks for a few details from BesTest’s Project Settings in your Jira - that is what lets us enable exactly your site and user.

Frequently asked questions

Is this the Jira MCP?

No. Atlassian ships its own MCP (the Rovo MCP Server) covering Jira and Confluence. BesTest ships a separate MCP covering your requirements, test cases, cycles, and coverage. Every vendor brings their own MCP; you add both to your agent and they work side by side in one conversation.

How does it fit Rovo and the Teamwork Graph?

Through your agent, the two pair up: Atlassian's MCP brings org-wide context, including Teamwork Graph tools in open beta, and the BesTest MCP brings the testing depth - requirements, test cases, and significance-weighted coverage together.

Do I need to know how to code?

No. You paste a few configuration lines into your agent once, following the docs, and from then on you use it by typing plain-language sentences.

Which agents work with it?

Any MCP-compatible client: Claude Code, Cursor, GitHub Copilot, Windsurf, Zed, Cline, and more. If your agent speaks MCP, it can talk to BesTest.

What can the agent touch? Is my data safe?

The agent acts as you, scoped to your Jira permissions, and beta access is granted per user, so nobody gets agent access without requesting it. It reads and writes only what you could read and write yourself.

When does the MCP reach general availability?

It is in closed beta today while we harden it, with GA coming soon. You can request access now through the support portal; the form asks for a few details from BesTest's Project Settings so we can enable exactly your site and user.

Works with your agent

Built on the Model Context Protocol, so it connects to Claude Code, Cursor, and any MCP-compatible client.

Getting started

Live in about a minute.

  1. ~30 seconds
    1.Install from the Marketplace

    One click on "Get it now" - no sales call, no signup form, no separate login.

  2. ~1 minute
    2.Enable it on a project

    Flip it on in project settings. BesTest shows up in the project menu, where your team already works.

  3. right away
    3.Run your first test

    Create a requirement, link a test case, hit run. No training course required.

Host your data in the EU, US, or IndiaNo Jira issue bloat - your library stays out of Jira’s wayBuilt on Atlassian Forge

Ready to Get Complete
Testing Visibility?

Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!

Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.

Start Free on Marketplace
Enterprise SecurityBuilt on Atlassian Forge.Built by TestersDesigned by QA professionals.Free to StartGet started for free and scale as you grow