[ E2E Testing ]
Record a Test
Use your MCP application normally while recording — every tool call, resource read, and widget interaction is captured as a step. Stop recording, give the test a name, and save. No code to write.
How to record
- 1
Click Record Test
Click the Record Test button in the top toolbar. The toolbar turns red to indicate recording is active.
mcp studio
Click Record Test to start capturing. - 2
Perform your actions
Use the app as normal. Every action you take is recorded as a test step. We are continuously adding support for more action types — if you see something missing, let us know.
Tool call
arguments, result, status
Resource read
URI, contents, status
Widget click
element selector, snapshot
Widget text input
element selector, value, snapshot
- 3
Stop, name, and save
Click Stop Record Test. Give the test a name and save it — it appears immediately in the Tests panel.
mcp studio
Stop recording, name the test, and save.
Tips
Keep recordings focused
One test per scenario. Short, focused tests are easier to debug when a step fails.
Record against a stable server
The saved baseline is compared on every replay. Recording against a server with random data will produce unreliable assertions — use shape or ignore mode to handle non-deterministic fields.
Tests follow the active profile
Recordings are not bound to a specific profile. Switch profiles before replaying to run the same test against a different environment.