Automating Pact Test Generation with the SmartBear MCP Server and PactFlow
Here is a new video demo showing how developers can use the SmartBear MCP Server together with GitHub Copilot to automatically generate and run Pact Tests right inside Visual Studio Code. In this walkthrough, you’ll see how easy it is to: ✅ Connect Copilot to a locally running SmartBear MCP server ✅ Use MCP tools to generate Pact Tests from your existing API specs and templates ✅ Filter endpoints and control file naming to fit your workflow ✅ Validate and run the generated tests directly from your terminal This example highlights how MCP can act as the bridge between your AI assistant and SmartBear’s quality ecosystem, turning natural language prompts into real, executable tests no manual setup required. Watch the full demo here: Automating PACT Tests with SmartBear MCP Server If you’re experimenting with your own MCP integrations or have ideas for other test automation workflows you’d like to see, drop your thoughts below!What’s Next for SmartBear’s MCP Server?
Over the past few months, we've been busy adding tools to the SmartBear MCP server with updates/releases happening every few weeks. We’ve seen teams begin exploring how MCP can securely connect SmartBear’s API, testing, and observability tools directly into their AI assistants and IDEs with no extra setup or manual data wrangling required. Here’s what early users are getting excited about: Full Context in One Place: Developers can instantly access API definitions, test outcomes, and error insights from tools like SwaggerHub, Zephyr, and BugSnag without leaving their workflow. Agentic Automation: Teams are building AI-driven workflows that trigger tests, surface flaky results, and even connect runtime errors to missing API documentation. Secure Local Control: All data stays protected under your organization’s governance policies. MCP simply makes it easier and safer to access what you already own. Next up, we’re focusing on real-world use cases like error-driven API refinement (BugSnag + Swagger) and automated validation after fixes (BugSnag + Reflect) to show how cross-product workflows can speed up release confidence. Here is a video from a SmartBear that has been exploring how to desgin APIs and ensure best practices around API Standardization. Swagger API Governance with MCP We’d love to hear how you’re experimenting with MCP whether it’s inside your IDE, your assistant, or your CI pipeline. Drop your feedback or share what workflows you’d like to see next!