Tired of juggling requirements in Jira, code in GitHub, and tests in separate tools? For years, this disconnected dev workflow has been a major pain point, making it tough to ensure your code changes align with requirements and your tests are always up-to-date.
The advent of generative AI has opened new doors and allowed us to develop and explore tools that make these aspirations a reality. The Model Context Protocol (MCP) provides the missing link, allowing AI tools to communicate with external applications, finally bridging the gap between your requirements, code, and tests.
At mabl, we believe this is a foundational shift, and we're excited to announce the launch of our own MCP server—a single, powerful gateway to your entire mabl workspace. Now, you can bring mabl's capabilities directly into your development environment, empowering AI to help you build and validate with unprecedented speed.
This isn’t just a new feature; it’s a new way to work. Let’s look at a few examples of how the mabl MCP server streamlines work for developers and quality teams.
A developer is working on a new feature and wants to quickly validate a code change. Instead of jumping to a separate UI, they simply open their IDE and ask their AI assistant:
"Hey Copilot, run the 'checkout test’ locally and give me the results."
The mabl MCP server receives the request, runs the test locally, and streams the results directly back to the developer within their IDE. The developer gets immediate feedback, identifies a bug, and fixes it on the spot, all without breaking their flow.
A QA engineer is tasked with creating a new end-to-end test. They have a Jira ticket with the user story and acceptance criteria. Using the mabl MCP server and their AI assistant, they can create the test with a single prompt:
"Copilot, create a new mabl browser test based on the details in this Jira ticket: TICKET-123."
The mabl MCP server connects to the Jira MCP server, pulls in the details, and automatically generates a structured mabl test. This intelligent workflow saves time, reduces manual effort, and ensures tests are accurately aligned with requirements from day one.
A quality manager needs a quick status update on a recent deployment. They don’t want to sift through dashboards or ask their team for a report. Instead, they use their AI desktop client to query the mabl MCP server:
"Claude, summarize the results of the 'production deployment' plan from the last 24 hours. Show me the pass/fail rate and provide details for test failures."
mabl MCP provides a concise summary, and the manager gets the high-level information they need immediately, empowering them to make faster decisions and communicate with stakeholders confidently.
This is just the beginning. The mabl MCP server is a foundational component that opens the door to even more powerful, agentic workflows. We're already working on the next generation of features. Imagine a future where mabl can automatically suggest relevant tests for your code changes—because it understands the relationship between your new code and your existing tests. These are the kinds of powerful, end-to-end workflows that the mabl MCP server will enable. We’re building a future where quality is an active, intelligent partner in your dev process, not a separate task.
Ready to get started? Visit our new mabl MCP server integration page to learn more and get started today. We’re excited to see what you build with it. Send along your feedback to the team here.