Summary
Everything here reads; nothing writes.
The 14 tools cover the reporting side of Cucumber Studio end to end — scenarios, action words, runs, executions, builds, environments — which is enough to answer why did this fail and what is this test really checking from an editor. Authoring, re-running and any repair still happen in Cucumber Studio itself, so this sits beside that workflow rather than replacing it.
What it is
A read-only client for Cucumber Studio, 14 tools covering projects, scenarios, action words, test runs, executions, builds and execution environments.
What you get
- Projects listed for the authenticated account and fetched in detail, with filtering and pagination on the list calls
- Scenarios listed per project, fetched individually, or found by the tags they carry
- Action words — the reusable steps a scenario is assembled from — listed, fetched and searched by tag, so a scenario can be read down to what it actually does
- Test runs listed and fetched, with cucumberstudio_get_test_executions returning the individual results inside a run
- Builds listed and fetched for a project
- Execution environments listed, which is how a result gets tied to where it ran
Requirements
A Cucumber Studio account with API access, supplying CUCUMBERSTUDIO_ACCESS_TOKEN, CUCUMBERSTUDIO_CLIENT_ID and CUCUMBERSTUDIO_UID.
Setup effort
One command plus a key — npx cucumberstudio-mcp, then supply credentials