Testing
Verify your MCP server works correctly across clients and models with automated test suites.
The Testing tab (Beta) runs automated test suites against your server. A suite describes scenarios, prompts and expected behavior, and Manufact executes them across different MCP clients and LLM models, because a server that works in one client can still fail in another.
Creating a suite
- Go to Testing and click Add test suite.
- Define the scenarios to test: what to ask, and what a correct response looks like.
- Pick the clients and models to run against, Inspector and ChatGPT are available today, with Claude and Cursor coming soon.
Running and reading results
Run a suite on demand from the list. Open a suite to see run history with pass/fail per client and model, regressions that only affect a specific client or model stand out immediately.
When to run tests
- Before publishing: alongside the Checklist, to make sure behavior matches your tool descriptions.
- After changing tool schemas: renamed tools and changed parameters are the most common source of silent client breakage.
- When upgrading frameworks: verify your MCP framework upgrade didn't change wire behavior.
Testing works for both Manufact-hosted and external servers.