AI-Supported Testing,
Grounded in Your Requirements.
Connect your coding agent to BesTest over MCP. It reads your requirements, test cases and results, generates automated tests in Playwright or any language, and syncs results back - while your code stays in your own repo.
Now in beta. You create your own token in the app. See how →
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.
What is our coverage on the checkout requirements, and which gap is riskiest?
+ more
Atlassian ships thisAtlassian MCPOfficially the Rovo MCP Server. Most people say "the Jira MCP".
idle - no Jira call needed here
We ship thisBesTest MCPIn beta. Create your own token in the app. GA soon.
What lands
Coverage at 71%, with the riskiest gap named rather than just the lowest one.
Riskiest is not simply lowest: significance weights complexity times impact.
Plan in Jira. Test in BesTest. One conversation.
Illustrative conversation · the BesTest MCP is in 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.
Start from a real problem.
Each guide takes one pain, shows the old way next to the agent way, and hands you the exact prompt to try.
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.
Connect
Create a token in BesTest, under API & MCP tokens in the app menu: one project, read-only or read-write, always with an expiry. Your agent connects over our MCP server and never sees more than you are allowed to see.
Understand
Agents read requirements, test cases, cycles, executions and the links between them to work out what actually needs testing, grounded in your real project data instead of guesswork.
Act
Draft test cases from requirement context, then record automated results from CI against the cycle through the REST API. Manual and automated runs land side by side, against the same requirements.
Add Atlassian's own MCP alongside ours: theirs brings Jira, Confluence, and Teamwork Graph context, ours brings requirements, test cases and their results. Your agent reasons over both in one conversation, with permissions intact.
You create your own token in the app. See how →
Agents write the tests. You stay in control.
Acts as you
Everything the agent reads or writes stays inside your own Jira permissions.
Scoped tokens
Each token reaches one project, read-only or read-write, and always expires. Admins can revoke any of them.
Hardened before GA
In beta, with the permission model your security team can approve.
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 executions. 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 with their significance, test cases, and results 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. It connects with a token you create yourself, which reaches one Space, can be read-only, and always expires; a Space admin can see and revoke every token pointed at their Space. It reads and writes only what you could read and write yourself.
When does the MCP reach general availability?
It is in beta today, with GA coming soon. There is no request form: you create your own token inside BesTest, from API & MCP tokens in the app menu. A token reaches one Space, at read-only or read-and-write, and you can revoke it whenever you like.
Works with your agent
Built on the Model Context Protocol, so it connects to Claude Code, Cursor, and any MCP-compatible client.
Live in about a minute.
- ~30 seconds1.Install from the Marketplace
One click on "Get it now" - no sales call, no signup form, no separate login.
- ~1 minute2.Enable it on a Space
Flip it on in Space settings. BesTest shows up in the Space menu, where your team already works.
- right away3.Run your first test
Create a requirement, link a test case, hit run. No training course required.
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